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: kyzevan23(at)mail(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Subject: Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date: 2026-05-20 10:03:23
Message-ID: CAHGQGwG=F8_12nPKxUkYm-uS5QFJp+KF=3X5zM2vKP=0SKAeHw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 20, 2026 at 1:37 PM Ayush Tiwari
<ayushtiwari(dot)slg01(at)gmail(dot)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.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrei Lepikhov 2026-05-20 10:55:24 Re: Fwd: Non-cancellable queries
Previous Message PG Bug reporting form 2026-05-20 09:23:35 BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade