Re: [PATCH] Fix LISTEN startup race with direct advancement

From: Arseniy Mukhin <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com>
To: Joel Jacobson <joel(at)compiler(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Fix LISTEN startup race with direct advancement
Date: 2026-05-20 17:27:51
Message-ID: CAE7r3MLi9MRfysi+0AcEBzO-tR1PCDr40KT7E+Qgpa9WZHZhmg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 20, 2026 at 2:20 PM Joel Jacobson <joel(at)compiler(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxime Schoemans 2026-05-20 17:44:52 Multi-Entry Indexing for GiST & SP-GiST
Previous Message Fujii Masao 2026-05-20 16:26:53 Re: Deadlock detector fails to activate on a hot standby replica