Re: Conflict detection for update_deleted in logical replication

Hello!

Sorry for being noisy - just want to remind: conflict detection system
(including new updated_deleted) is giving invalid reports because of
the issue related to SnapshotDirty vs btree. So, it is not possible to
rely on that at the moment.

You may check TAP tests here [0] and some explanation here [1] and
here [2]. Set $simulate_race_condition to disable race condition in
tests.

Invalid conflicts so far (valid/detected):
* delete_origin_differs/delete_missing
* update_origin_differs/update_missing
* update_origin_differs/update_deleted

Best regards,
Mikhail.

[0]: https://commitfest.postgresql.org/patch/5151/
[1]:
https://www.postgresql.org/message-id/flat/CADzfLwWC49oanFSGPTf%3D6FJoTw-kAnpPZV8nVqAyR5KL68LrHQ%40mail.gmail.com#5f6b3be849f8d95c166decfae541df09
[2]:
https://www.postgresql.org/message-id/flat/CADzfLwWuXh8KO%3DOZvB71pZnQ8nH0NYXfuGbFU6FBiVZUbmuFGg%40mail.gmail.com#76f98a9ae3479bbaf5ee9262322d466e