Request a Demo
Home   >   mailing lists

Re: Fix apply worker crash when subscriber table has only a deferrable primary key - Mailing list pgsql-hackers

From Nisha Moond
Subject Re: Fix apply worker crash when subscriber table has only a deferrable primary key
Date
Msg-id CABdArM7eVtS5wF696UgBEgjkDih-vTgqJxE9G4R=G95pJc9G4w@mail.gmail.com
Whole thread
In response to RE: Fix apply worker crash when subscriber table has only a deferrable primary key  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
Tree view 
On Tue, Sep 29, 2026 at 3:20 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> > Thanks for the patch, I've combined your suggested fix and attched
> > updated patch v2.
>
> I checked and no comments for the implementation.
> Regarding the back patch, the initial issue (FindReplTupleInLocalRel() can cause
> a crash) should be done till PG17, but second one (RelationFindDeletedTupleInfoSeq()
> can do a wrong decision) should be done only for PG19/master, right?

Makes sense; I overlooked the fact.

> If so the patch should be separated. Also, a test can be added in 035_conflicts for the
> second issue.
>

I’ve attached the separate patches; both apply independently on HEAD
and their respective backport branches.

I’ve also added a test case in 035_conflicts.pl, for the
RelationFindDeletedTupleInfoSeq() fix.

--
Thanks,
Nisha
Attachment

pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: injection_points: canceled or terminated waiters leak their wait slots
Next
From: Manu
Date:
Subject: Re: BUG #19686: Rolling back SET TABLESPACE