| From: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(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-21 11:48:34 |
| Message-ID: | CAJTYsWXEpdWt57Vu13-5aEROVfq+G+zgAzZUwzAtFfYyfYDhHw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
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!
Regards,
Ayush
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PetSerAl | 2026-05-21 18:41:51 | Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT |
| Previous Message | Alexander Korotkov | 2026-05-21 11:31:44 | Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always |