Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()
Date
Msg-id CAA4eK1K-1LDc4hkz1Da7eFzGp-sG9V3xNEg23Lahr-5xp-i_hg@mail.gmail.com
Whole thread Raw
In response to RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()  (Amit Kapila <amit.kapila16@gmail.com>)
RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder()  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-bugs
On Wed, Mar 13, 2024 at 3:24 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> Regarding the second failure, which was reported the upstream.
>
> While reading some other threads, I found that the similar phenomenon has already
> been reported in [1]. The primal reason was that slots reused the serialized
> snapshot but it was not correct. Therefore, I thought the second failure should
> be discussed on the referred thread and here we should focused on the recently
> proposed fix by me.
> (This meant that my proposed workload may not work well after the fix. Will modify
> the test later if needed.)
>

I agree with this. Is there a reason you are not using the test for
the issue originally reported in this thread?

--
With Regards,
Amit Kapila.



pgsql-bugs by date:

Previous
From: Arnd Baranowski
Date:
Subject: Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
Next
From: Noah Misch
Date:
Subject: Re: FSM Corruption (was: Could not read block at end of the relation)