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

Alexander Korotkov <aekorotkov@gmail.com>

From: Alexander Korotkov <aekorotkov@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Ayush Tiwari <ayushtiwari.slg01@gmail.com>, kyzevan23@mail.ru, pgsql-bugs@lists.postgresql.org
Date: 2026-05-20T11:31:27Z
Lists: pgsql-bugs

Attachments

On Wed, May 20, 2026 at 1:03 PM Fujii Masao <masao.fujii@gmail.com> wrote:
> On Wed, May 20, 2026 at 1:37 PM Ayush Tiwari
> <ayushtiwari.slg01@gmail.com> wrote:
> > Thanks for the report and the precise repro.
>
> +1
>
> > Attached patch adds a RecoveryInProgress() check to skip the cleanup
> > branch on standbys.
>
> Thanks for investigating this issue and for the patch!
> The patch looks good to me.
>
> > I think this needs to be backpatched too.
>
> Yes. Seems this should be backpatched to v17, where login event triggers
> were introduced.

I've added a tap test reproducing the bug.  I'm going to push and
backpatch this to v17 if no objections.

------
Regards,
Alexander Korotkov
Supabase

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Skip pg_database.dathasloginevt cleanup on standby