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

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, kyzevan23(at)mail(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
Date: 2026-05-25 08:53:57
Message-ID: CAPpHfdtG_ELhqDwsq0yHq_OWHVP-fw2evtL2yQjG-n2ZaFq8iQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, May 21, 2026 at 2:48 PM Ayush Tiwari
<ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
> On Thu, 21 May 2026 at 17:01, Alexander Korotkov <aekorotkov(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-05-25 15:12:41 Re: BUG #19491: Segmentation fault triggered by IS NULL
Previous Message zengman 2026-05-24 05:15:43 Re:BUG #19492: intarray: fix variable stats leak in _int_matchsel