Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, kyzevan23(at)mail(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date: 2026-10-15 02:55:45
Message-ID: CAHGQGwFZe2+q3iqJY1J=jzMKcLAehDFr3ayRzeMX0PS8N4E2aA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Oct 9, 2026 at 1:53 PM Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
> Thanks for tracking this down. Since the cleanup deliberately doesn't wait
> for the database lock, I think the test should allow another attempt
> instead of assuming that the first login clears the flag?

+1

> The attached patch retries fresh connections to regress_login_evt until
> the flag is cleared.

Thanks for the patch! LGTM.
Barring any objections, I will commit it.

Regards,

--
Fujii Masao

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message David Rowley 2026-10-15 02:53:14 Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows