| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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>, ocean_li_996 <ocean_li_996(at)163(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Subject: | Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() |
| Date: | 2024-03-15 12:46:02 |
| Message-ID: | CAA4eK1K-1LDc4hkz1Da7eFzGp-sG9V3xNEg23Lahr-5xp-i_hg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Mar 13, 2024 at 3:24 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2024-03-16 03:03:39 | Re: FSM Corruption (was: Could not read block at end of the relation) |
| Previous Message | Arnd Baranowski | 2024-03-15 09:54:34 | Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue |