From: | ocean_li_996 <ocean_li_996(at)163(dot)com> |
---|---|
To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "'Amit Kapila'" <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "feichanghong(at)qq(dot)com" <feichanghong(at)qq(dot)com>, "Alexander Lakhin" <exclusion(at)gmail(dot)com> |
Subject: | Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() |
Date: | 2024-03-19 02:58:38 |
Message-ID: | 1ed0d70a.4ec5.18e54a587dd.Coremail.ocean_li_996@163.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Dear Hayato, Amit,
At 2024-03-18 14:44:46, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>Dear Amit,
>
>> I agree with this. Is there a reason you are not using the test for
>> the issue originally reported in this thread?
>
>Firstly the modified version was used to shorten the test workload.
>However, the optimization assumed the BUG which may be fixed in future.
>Here are new patch set which recent changes for testcases were reverted.
>
>Best Regards,
>Hayato Kuroda
>FUJITSU LIMITED
>https://www.fujitsu.com/
>
The spec test added in latest patch only involves a single logical replication slot.
IIUC, the issue can be fixed independently, without having to wait for the issue
in [1] to be resolved first.
[1] https://www.postgresql.org/message-id/29273AF3-9684-4069-9257-D05090B03B99@amazon.com
Best Regards,
Haiyang Li
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-03-19 03:57:51 | Re: ReplicationSlotRelease may set the statusFlags of other processes in PG14 |
Previous Message | Amit Kapila | 2024-03-19 02:33:06 | Re: Potential data loss due to race condition during logical replication slot creation |