| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Cc: | "feichanghong(at)qq(dot)com" <feichanghong(at)qq(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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-13 09:54:36 |
| Message-ID: | TYCPR01MB12077B8B93B0634B4C7C1B132F52A2@TYCPR01MB12077.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dear hackers,
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.)
[1]: https://www.postgresql.org/message-id/flat/2444AA15-D21B-4CCE-8052-52C7C2DAFE5C%40amazon.com
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
https://www.fujitsu.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-03-13 11:18:25 | BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3 |
| Previous Message | Hayato Kuroda (Fujitsu) | 2024-03-13 09:47:01 | RE: Potential data loss due to race condition during logical replication slot creation |