Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always - Mailing list pgsql-bugs

From Fujii Masao
Subject Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date
Msg-id CAHGQGwG=F8_12nPKxUkYm-uS5QFJp+KF=3X5zM2vKP=0SKAeHw@mail.gmail.com
Whole thread
In response to Re: [PATCH] Cover get_json_table_plan() with tests  ("Jonathan Gonzalez V." <jonathan.abdiel@gmail.com>)
Responses Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
List pgsql-bugs
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.

Regards,

--
Fujii Masao



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
Next
From: Andrei Lepikhov
Date:
Subject: Re: Fwd: Non-cancellable queries