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

From Alexander Korotkov
Subject Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date
Msg-id CAPpHfdtG_ELhqDwsq0yHq_OWHVP-fw2evtL2yQjG-n2ZaFq8iQ@mail.gmail.com
Whole thread
In response to Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always  (Ayush Tiwari <ayushtiwari.slg01@gmail.com>)
List pgsql-bugs
On Thu, May 21, 2026 at 2:48 PM Ayush Tiwari
<ayushtiwari.slg01@gmail.com> wrote:
> 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!

Thank you.  I'm going to push and backpatch it if no objections.

------
Regards,
Alexander Korotkov
Supabase



pgsql-bugs by date:

Previous
From: "zengman"
Date:
Subject: Re:BUG #19492: intarray: fix variable stats leak in _int_matchsel
Next
From: Ayush Tiwari
Date:
Subject: Re: BUG #19491: Segmentation fault triggered by IS NULL