From: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Notify downstream to discard the streamed transaction which was aborted due to crash. |
Date: | 2023-01-06 05:44:16 |
Message-ID: | OS0PR01MB5716A83F73F46E53A3D382F294FB9@OS0PR01MB5716.jpnprd01.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday, January 6, 2023 1:15 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Fri, Jan 6, 2023 at 9:25 AM houzj(dot)fnst(at)fujitsu(dot)com <houzj(dot)fnst(at)fujitsu(dot)com>
> wrote:
> >
> >
> > To fix it, One idea is to send a stream abort message when we are
> > cleaning up crashed transaction on publisher(e.g. in
> > ReorderBufferAbortOld()). And here is a tiny patch which changes the
> > same. I have confirmed that the bug is fixed and all regression tests
> > pass. I didn't add a testcase because we need to make sure the crash
> > happens before all the WAL logged transactions data are decoded which
> doesn't seem easy to write a stable test for this.
> >
>
> Your fix looks good to me. Have you tried this in PG-14 where it was
> introduced?
Yes, I have confirmed that PG-14 has the same problem and can be fixed after
applying the patch.
Best regards,
Hou zj
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2023-01-06 05:48:29 | Re: Notify downstream to discard the streamed transaction which was aborted due to crash. |
Previous Message | Nathan Bossart | 2023-01-06 05:40:17 | Re: wake up logical workers after ALTER SUBSCRIPTION |