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

From Ayush Tiwari
Subject Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date
Msg-id CAJTYsWXEpdWt57Vu13-5aEROVfq+G+zgAzZUwzAtFfYyfYDhHw@mail.gmail.com
Whole thread
In response to Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
List 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

pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Next
From: PetSerAl
Date:
Subject: Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT