Horton
Menu

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

Ayush Tiwari <ayushtiwari.slg01@gmail.com>

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

On Thu, 21 May 2026 at 17:01, Alexander Korotkov <aekorotkov@gmail.com>
wrote:

>
> I suggest another approach.  Create a separate test database and apply
> event trigger on it.  wait_for_catchup() and others use 'postgres'
> database and wouldn't touch our test database.
> I also added check for successful clearance of the flag on both
> primary and standby.  One issue spotted there: in-place heap update
> doesn't issue a WAL flush.  But I think that's minor, WAL could be
> flushed by any subsequent operation.


I agree the approach you are suggesting is better.

Patch looks good to me!

Regards,
Ayush

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