mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-14 02:39:16 +02:00
19890a064e
Commit 0aa8a01d04 extends the output plugin API to allow decoding of
prepared xacts and allowed the user to enable/disable the two-phase option
via pg_logical_slot_get_changes(). This can lead to a problem such that
the first time when it gets changes via pg_logical_slot_get_changes()
without two_phase option enabled it will not get the prepared even though
prepare is after consistent snapshot. Now next time during getting changes,
if the two_phase option is enabled it can skip prepare because by that
time start decoding point has been moved. So the user will only get commit
prepared.
Allow to enable/disable this option at the create slot time and default
will be false. It will break the existing slots which is fine in a major
release.
Author: Ajin Cherian
Reviewed-by: Amit Kapila and Vignesh C
Discussion: https://postgr.es/m/d0f60d60-133d-bf8d-bd70-47784d8fabf3@enterprisedb.com
54 lines
2.0 KiB
Ruby
54 lines
2.0 KiB
Ruby
# Test decoding of two-phase transactions during the build of a consistent snapshot.
|
|
setup
|
|
{
|
|
DROP TABLE IF EXISTS do_write;
|
|
CREATE TABLE do_write(id serial primary key);
|
|
}
|
|
|
|
teardown
|
|
{
|
|
DROP TABLE do_write;
|
|
SELECT 'stop' FROM pg_drop_replication_slot('isolation_slot');
|
|
}
|
|
|
|
|
|
session "s1"
|
|
setup { SET synchronous_commit=on; }
|
|
|
|
step "s1init" {SELECT 'init' FROM pg_create_logical_replication_slot('isolation_slot', 'test_decoding', false, true);}
|
|
step "s1start" {SELECT data FROM pg_logical_slot_get_changes('isolation_slot', NULL, NULL, 'include-xids', 'false', 'skip-empty-xacts', '1');}
|
|
step "s1insert" { INSERT INTO do_write DEFAULT VALUES; }
|
|
|
|
session "s2"
|
|
setup { SET synchronous_commit=on; }
|
|
|
|
step "s2b" { BEGIN; }
|
|
step "s2txid" { SELECT pg_current_xact_id() IS NULL; }
|
|
step "s2c" { COMMIT; }
|
|
step "s2insert" { INSERT INTO do_write DEFAULT VALUES; }
|
|
step "s2p" { PREPARE TRANSACTION 'test1'; }
|
|
step "s2cp" { COMMIT PREPARED 'test1'; }
|
|
|
|
|
|
session "s3"
|
|
setup { SET synchronous_commit=on; }
|
|
|
|
step "s3b" { BEGIN; }
|
|
step "s3txid" { SELECT pg_current_xact_id() IS NULL; }
|
|
step "s3c" { COMMIT; }
|
|
|
|
# Force building of a consistent snapshot between a PREPARE and COMMIT PREPARED
|
|
# and ensure that the whole transaction is decoded at the time of COMMIT
|
|
# PREPARED.
|
|
#
|
|
# 's1init' step will initialize the replication slot and cause logical decoding
|
|
# to wait in initial starting point till the in-progress transaction in s2 is
|
|
# committed. 's2c' step will cause logical decoding to go to initial consistent
|
|
# point and wait for in-progress transaction s3 to commit. 's3c' step will cause
|
|
# logical decoding to find a consistent point while the transaction s2 is
|
|
# prepared and not yet committed. This will cause the first s1start to skip
|
|
# prepared transaction s2 as that will be before consistent point. The second
|
|
# s1start will allow decoding of skipped prepare along with commit prepared done
|
|
# as part of s2cp.
|
|
permutation "s2b" "s2txid" "s1init" "s3b" "s3txid" "s2c" "s2b" "s2insert" "s2p" "s3c" "s1insert" "s1start" "s2cp" "s1start"
|