RE: Potential data loss due to race condition during logical replication slot creation
Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Amit Kapila' <amit.kapila16@gmail.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, "Callahan, Drew" <callaan@amazon.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-03-19T04:39:30Z
Lists: pgsql-bugs
Attachments
- v2-0001-Serialize-running-xacts.patch (application/octet-stream) patch v2-0001
Dear Amit, > > Won't it be possible to achieve the same thing if we just save > (serialize) the highest xid among all running xacts? > Indeed, here is an updated version. Since the array in xl_running_xact is not ordered, entries of it must be seeked and found the highest one. Best Regards, Hayato Kuroda FUJITSU LIMITED https://www.fujitsu.com/
Commits
-
Fix possibility of logical decoding partial transaction changes.
- bb19b70081e2 18.0 landed
- 068674f4ab44 17.0 landed
- 2f3304ce133f 16.4 landed
- aee8c2b95492 15.8 landed
- f7d3caf9ddbf 14.13 landed
- cf2c69ec5a5b 13.16 landed
- 1b370758770c 12.20 landed