| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: Trigger violates foreign key constraint |
| Date: | 2023-10-30 21:08:55 |
| Message-ID: | 169870013508.94390.6664069465416827376.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation: tested, passed
It seems like people have been talking about this problem since 2010 (https://stackoverflow.com/questions/3961825/foreign-keys-in-postgresql-can-be-violated-by-trigger) and we finally got our act together and put it in the official document today, only 13 years later.
The new status of this patch is: Ready for Committer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-10-30 21:50:58 | Re: Trigger violates foreign key constraint |
| Previous Message | Nathan Bossart | 2023-10-30 21:01:28 | Re: always use runtime checks for CRC-32C instructions |