aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-12-14 10:58:33 +0900
committerMichael Paquier <michael@paquier.xyz>2021-12-14 10:58:33 +0900
commit65af1e842208cf3edec3b74842eec87b4a0138e5 (patch)
treee8cc0480b694dcb4ba63165ce5415d832939d2a5 /src/backend/access/transam/commit_ts.c
parenta5fe66bfdaec7add9381b61b33f5c361eaacd055 (diff)
downloadpostgresql-65af1e842208cf3edec3b74842eec87b4a0138e5.tar.gz
postgresql-65af1e842208cf3edec3b74842eec87b4a0138e5.zip
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
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions