| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Manu <manuelreyesbravo(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Zhijie Hou <houzj(dot)fnst(at)fujitsu(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [BUG?] check_exclusion_or_unique_constraint false negative |
| Date: | 2026-10-05 22:36:00 |
| Message-ID: | CADzfLwUKAnaaadNFmVXk+ED=dStL_FOU0jFzbzVPmA0NW-xstA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, Manu!
Thanks a lot for the review, especially for the rebase and the
in-flight INSERT case.
The logical replication part has had its own thread for a while [1], so
I've replied there and posted v20 there as well.
In short, the behavior change is real and is now described in the commit
message. I think master only happens to win a race in that case rather
than providing a guarantee, so v20 leaves the wait out. More details
are in [1].
[1]: https://postgr.es/m/CADzfLwXZVmbo11tFS_G2i+6TfFVwHU4VUUSeoqb+8UQfuoJs8A@mail.gmail.com
Best regards,
Mikhail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Detomini | 2026-10-05 22:37:08 | Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names |
| Previous Message | Tom Lane | 2026-10-05 22:35:58 | Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF |