| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sergey Belyashov <sergey(dot)belyashov(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18815: Logical replication worker Segmentation fault |
| Date: | 2025-04-08 05:59:53 |
| Message-ID: | CAA4eK1KWhm8dcGb4OUHTbA+UhC=2+T-k+=pBTq1CjdWaiTeAbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Apr 7, 2025 at 3:28 PM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> > What is the
> > behavior of conflict reporting code in case of exclusion constraints?
>
> Under logical replication context, since we do not detect conflicts for exclusion
> constraints, it would simply report the original constraint violation ERROR.
>
Fair enough. On considering it again, I find your idea of building
conflict-related information when it is actually required sounds
better, as it may also save us performance in some corner cases.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou (Fujitsu) | 2025-04-08 06:56:25 | RE: BUG #18815: Logical replication worker Segmentation fault |
| Previous Message | Laurenz Albe | 2025-04-08 05:50:56 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-04-08 06:11:04 | Re: BAS_BULKREAD vs read stream |
| Previous Message | Nico Williams | 2025-04-08 05:46:48 | Re: pg16 && GSSAPI && Heimdal/Macos |