Horton

Re: Foreign key isolation tests

Paul A Jungwirth <pj@illuminatedcomputing.com>

View thread View on postgr.es
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, Rustam ALLAKOV <rustamallakov@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-11T20:18:03Z
Lists: pgsql-hackers

Attachments

On Mon, Aug 11, 2025 at 8:03 AM Robert Haas <robertmhaas@gmail.com> wrote:
>
> 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.

Ugh, sorry about that. Here is a fix.

Yours,

-- 
Paul              ~{:-)
pj@illuminatedcomputing.com

Commits

  1. Improve comment about snapshot macros

  2. Add test for temporal referential integrity

  3. Fill testing gap for possible referential integrity violation

  4. Simplify COALESCE() with one surviving argument.