Michael Paquier 8abb6c27ec Remove assertion for replication origins in PREPARE TRANSACTION ... When using replication origins, pg_replication_origin_xact_setup() is an optional choice to be able to set a LSN and a timestamp to mark the origin, which would be additionally added to WAL for transaction commits or aborts (including 2PC transactions). An assertion in the code path of PREPARE TRANSACTION assumed that this data should always be set, so it would trigger when using replication origins without setting up an origin LSN. Some tests are added to cover more this kind of scenario. Oversight in commit 1eb6d65. Per discussion with Amit Kapila and Masahiko Sawada. Discussion: https://postgr.es/m/YbbBfNSvMm5nIINV@paquier.xyz Backpatch-through: 11		2021-12-14 10:58:37 +09:00
..
binary.sql
ddl.sql	Relax overly strict assertion	2019-02-12 18:42:37 -03:00
decoding_in_xact.sql
decoding_into_rel.sql	Fix crash when logical decoding is invoked from a PL function.	2017-10-06 19:18:58 -04:00
messages.sql
permissions.sql
prepared.sql
replorigin.sql	Remove assertion for replication origins in PREPARE TRANSACTION	2021-12-14 10:58:37 +09:00
rewrite.sql	Fix potential assertion failure when reindexing a pg_class index.	2019-04-29 19:42:09 -07:00
slot.sql	Fix logical replication slot initialization	2018-08-01 17:39:07 -04:00
spill.sql	Make contrib/test_decoding regression tests safe for CZ locale.	2016-11-21 20:39:28 -05:00
time.sql
toast.sql	Fix toast rewrites in logical decoding.	2021-08-25 09:43:33 +05:30
truncate.sql	Logical decoding of TRUNCATE	2018-04-07 11:34:10 -04:00
xact.sql	Don't propagate a null subtransaction snapshot up to parent transaction.	2016-08-07 13:15:55 -04:00