postgres/contrib/test_decoding/sql/truncate.sql

-- predictability
SET synchronous_commit = on;

SELECT 'init' FROM pg_create_logical_replication_slot('regression_slot', 'test_decoding');

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;

SELECT data FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1');
Force synchronous commit to be enabled for all test_decoding tests. Without that the tests fail when forced to be run against a cluster with synchronous_commit = off (as the WAL might not yet be flushed to disk by the point logical decoding gets called, and thus the expected output breaks). Most tests already do that, add it to a few newer tests. Author: Andres Freund 2018-10-10 13:53:02 -07:00			`-- predictability`
			`SET synchronous_commit = on;`

Logical decoding of TRUNCATE Add a new WAL record type for TRUNCATE, which is only used when wal_level >= logical. (For physical replication, TRUNCATE is already replicated via SMGR records.) Add new callback for logical decoding output plugins to receive TRUNCATE actions. Author: Simon Riggs <simon@2ndquadrant.com> Author: Marco Nenciarini <marco.nenciarini@2ndquadrant.it> Author: Peter Eisentraut <peter.eisentraut@2ndquadrant.com> Reviewed-by: Petr Jelinek <petr.jelinek@2ndquadrant.com> Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Alvaro Herrera <alvherre@alvh.no-ip.org> 2018-04-07 11:17:56 -04:00			`SELECT 'init' FROM pg_create_logical_replication_slot('regression_slot', 'test_decoding');`

			`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;`

			`SELECT data FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1');`