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

On Sunday, March 21, 2021 4:37 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>I have further updated the patch to implement unique GID on the
>subscriber-side as discussed in the nearby thread [1].

I did some tests(cross version & synchronous) on the latest patch set v65*, all tests passed. Here is the detail,
pleasetake it as a reference.
 

Case   |  version of publisher  |  version of subscriber  |  two_phase option    |  synchronous  |  expect result  |
result

-------+------------------------+-------------------------+----------------------+---------------+-----------------+---------
 1     |  13                    |  14(patched)            |  on                  |  no           |  same as case3  |
ok
 2     |  13                    |  14(patched)            |  off                 |  no           |  same as case3  |
ok
 3     |  13                    |  14(unpatched)          |  not support         |  no           |  -              |
-
 4     |  14(patched)           |  13                     |  not support         |  no           |  same as case5  |
ok
 5     |  14(unpatched)         |  13                     |  not support         |  no           |  -              |
-
 6     |  13                    |  14(patched)            |  on                  |  yes          |  same as case8  |
ok
 7     |  13                    |  14(patched)            |  off                 |  yes          |  same as case8  |
ok
 8     |  13                    |  14(unpatched)          |  not support         |  yes          |  -              |
-
 9     |  14(patched)           |  13                     |  not support         |  yes          |  same as case10 |
ok
 10    |  14(unpatched)         |  13                     |  not support         |  yes          |  -              |
-

remark:
    (1)case3, 5 ,8, 10 is tested just for reference
    (2)SQL been executed in each case
       scenario1    begin…commit
       scenario2    begin…prepare…commit

Regards,
Tang