Re: BUG #18815: Logical replication worker Segmentation fault

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-09 09:29:22
Message-ID: CAA4eK1KTbQGVQcypVMnvo=69nf_PY2if6FLC6O+t99WqxeZ+cw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, Apr 8, 2025 at 12:26 PM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
>
> I am attaching the V2 patch which implements this idea by
> postponing index info initialization until the FindConflictTuple(). I confirmed
> It can pass regression and pgindent check.
>

Thanks, I pushed this patch yesterday.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-04-09 13:46:29 BUG #18885: ERROR: corrupt MVNDistinct entry - 2
Previous Message David Rowley 2025-04-09 02:55:33 Re: Error when using array_agg with filter where clause in pg16 and pg17

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-04-09 09:39:49 Re: pgsql: Make cancel request keys longer
Previous Message Kirill Reshke 2025-04-09 09:25:54 Re: tab complete for COPY populated materialized view TO