Re: [HACKERS] logical decoding of two-phase transactions

Please find attached the latest patch set v68*

Differences from v67* are:

* Rebased to HEAD @ today.

* v68 fixes an issue reported by Vignesh [1] where a scenario was
found which still was able to cause a generated GID clash. Using
Vignesh's test script I could reproduce the problem exactly as
described. The fix makes the GID unique by including the subid. Now
the same script runs to normal completion and produces good/expected
output:

 transaction |       gid        |           prepared            |
owner   | database
-------------+------------------+-------------------------------+----------+----------
         547 | pg_gid_16389_543 | 2021-03-30 10:32:36.87207+11  |
postgres | postgres
         555 | pg_gid_16390_543 | 2021-03-30 10:32:48.087771+11 |
postgres | postgres
(2 rows)


----
[1] https://www.postgresql.org/message-id/CALDaNm2ZnJeG23bE%2BgEOQEmXo8N%2Bfs2g4%3DxuH2u6nNcX0s9Jjg%40mail.gmail.com

Kind Regards,
Peter Smith.
Fujitsu Australia