2018-10-10 23:53:02 +03:00
|
|
|
-- predictability
|
|
|
|
SET synchronous_commit = on;
|
2018-04-07 18:17:56 +03:00
|
|
|
SELECT 'init' FROM pg_create_logical_replication_slot('regression_slot', 'test_decoding');
|
|
|
|
?column?
|
|
|
|
----------
|
|
|
|
init
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
CREATE TABLE tab1 (id serial unique, data int);
|
|
|
|
CREATE TABLE tab2 (a int primary key, b int);
|
|
|
|
TRUNCATE tab1;
|
|
|
|
TRUNCATE tab1, tab1 RESTART IDENTITY CASCADE;
|
|
|
|
TRUNCATE tab1, tab2;
|
2022-04-07 19:13:13 +03:00
|
|
|
SELECT data FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1');
|
2018-04-07 18:17:56 +03:00
|
|
|
data
|
|
|
|
------------------------------------------------------
|
|
|
|
BEGIN
|
|
|
|
table public.tab1: TRUNCATE: (no-flags)
|
|
|
|
COMMIT
|
|
|
|
BEGIN
|
|
|
|
table public.tab1: TRUNCATE: restart_seqs cascade
|
|
|
|
COMMIT
|
|
|
|
BEGIN
|
|
|
|
table public.tab1, public.tab2: TRUNCATE: (no-flags)
|
|
|
|
COMMIT
|
|
|
|
(9 rows)
|
|
|
|
|
Implement streaming mode in ReorderBuffer.
Instead of serializing the transaction to disk after reaching the
logical_decoding_work_mem limit in memory, we consume the changes we have
in memory and invoke stream API methods added by commit 45fdc9738b.
However, sometimes if we have incomplete toast or speculative insert we
spill to the disk because we can't generate the complete tuple and stream.
And, as soon as we get the complete tuple we stream the transaction
including the serialized changes.
We can do this incremental processing thanks to having assignments
(associating subxact with toplevel xacts) in WAL right away, and
thanks to logging the invalidation messages at each command end. These
features are added by commits 0bead9af48 and c55040ccd0 respectively.
Now that we can stream in-progress transactions, the concurrent aborts
may cause failures when the output plugin consults catalogs (both system
and user-defined).
We handle such failures by returning ERRCODE_TRANSACTION_ROLLBACK
sqlerrcode from system table scan APIs to the backend or WALSender
decoding a specific uncommitted transaction. The decoding logic on the
receipt of such a sqlerrcode aborts the decoding of the current
transaction and continue with the decoding of other transactions.
We have ReorderBufferTXN pointer in each ReorderBufferChange by which we
know which xact it belongs to. The output plugin can use this to decide
which changes to discard in case of stream_abort_cb (e.g. when a subxact
gets discarded).
We also provide a new option via SQL APIs to fetch the changes being
streamed.
Author: Dilip Kumar, Tomas Vondra, Amit Kapila, Nikhil Sontakke
Reviewed-by: Amit Kapila, Kuntal Ghosh, Ajin Cherian
Tested-by: Neha Sharma, Mahendra Singh Thalor and Ajin Cherian
Discussion: https://postgr.es/m/688b0b7f-2f6c-d827-c27b-216a8e3ea700@2ndquadrant.com
2020-08-08 05:04:39 +03:00
|
|
|
SELECT pg_drop_replication_slot('regression_slot');
|
|
|
|
pg_drop_replication_slot
|
|
|
|
--------------------------
|
|
|
|
|
|
|
|
(1 row)
|
|
|
|
|