Re: Trigger violates foreign key constraint

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Subject: Re: Trigger violates foreign key constraint
Date: 2024-04-18 12:24:39
Message-ID: CAJ7c6TOe5KfmkhkBi48LqL3otQ_rkn4P=xCt6oVci_rP6+Sukg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > Patch v3 is attached.
>
> I agree with documenting this hazard, but I think it'd be better
> to do so in the "Triggers" chapter. There is no hazard unless
> you are writing user-defined triggers, which is surely far fewer
> people than use foreign keys. So I suggest something like the
> attached.

I don't mind changing the chapter, but I prefer the wording chosen in
v3. The explanation in v4 is somewhat hard to follow IMO.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marcel Hofstetter 2024-04-18 12:57:14 Re: Solaris tar issues, or other reason why margay fails 010_pg_basebackup?
Previous Message Ranier Vilela 2024-04-18 12:07:43 Re: plenty code is confused about function level static