Re: Foreign key isolation tests
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Paul A Jungwirth <pj@illuminatedcomputing.com>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>,
Rustam ALLAKOV <rustamallakov@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-11T15:03:29Z
Lists: pgsql-hackers
On Fri, Jul 18, 2025 at 7:26 PM Paul A Jungwirth <pj@illuminatedcomputing.com> wrote: > Thanks for taking a look! Here are new patches with those extra tests. > There are extensive regress tests already, so I just tested the same > concurrency pattern. I think the results are okay. I do get a > can't-serialize exception for a couple valid changes under REPEATABLE > READ and SERIALIZE, but I think they are expected and not a bug. (I > think you would see the same thing outside of FKs.) 0001 and 0003 look OK to me on a quick read-through. 0002 seems to do something horrible to isolation_schedule. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
Improve comment about snapshot macros
- 1d5800019f68 19 (unreleased) landed
-
Add test for temporal referential integrity
- e8cec3d1791c 19 (unreleased) landed
-
Fill testing gap for possible referential integrity violation
- a2b4102a21ad 19 (unreleased) landed
-
Simplify COALESCE() with one surviving argument.
- 931766aaec58 19 (unreleased) cited