Re: [PATCH] Fix LISTEN startup race with direct advancement - Mailing list pgsql-hackers

From Arseniy Mukhin
Subject Re: [PATCH] Fix LISTEN startup race with direct advancement
Date
Msg-id CAE7r3MLi9MRfysi+0AcEBzO-tR1PCDr40KT7E+Qgpa9WZHZhmg@mail.gmail.com
Whole thread
In response to Re: [PATCH] Fix memory leak in pg_config  (Ivan Kush <ivan.kush@tantorlabs.com>)
Responses Re: [PATCH] Fix LISTEN startup race with direct advancement
List pgsql-hackers
On Wed, May 20, 2026 at 2:20 PM Joel Jacobson <joel@compiler.org> wrote:
>
> On Wed, May 20, 2026, at 04:01, Arseniy Mukhin wrote:
> > One point - looks like the 0003 contains the same test as 0001.
>
> They are similar, but if you look carefully you'll see that they use
> different injection points:
>
> 0001 uses async-notify-before-listen-commit
> 0002 uses async-notify-after-listen-commit
>

Yes, but I meant 0001 and 0003.  There are two specs:
  - async-notify-listen-startup.spec (added in 0001)
  - async-notify-listen-race.spec (added in 0003)
Looks identical, unless I missed something.


Best regards,
Arseniy Mukhin



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Implement waiting for wal lsn replay: reloaded
Next
From: Maxime Schoemans
Date:
Subject: Multi-Entry Indexing for GiST & SP-GiST