diff options
Diffstat (limited to 'src/test/recovery/t/036_truncated_dropped.pl')
-rw-r--r-- | src/test/recovery/t/036_truncated_dropped.pl | 136 |
1 files changed, 136 insertions, 0 deletions
diff --git a/src/test/recovery/t/036_truncated_dropped.pl b/src/test/recovery/t/036_truncated_dropped.pl new file mode 100644 index 00000000000..2d5339d9d8d --- /dev/null +++ b/src/test/recovery/t/036_truncated_dropped.pl @@ -0,0 +1,136 @@ +# Copyright (c) 2021-2023, PostgreSQL Global Development Group + +# Tests recovery scenarios where the files are shorter than in the common +# cases, e.g. due to replaying WAL records of a relation that was subsequently +# truncated or dropped. + +use strict; +use warnings; +use PostgreSQL::Test::Cluster; +use Test::More; + +my $node = PostgreSQL::Test::Cluster->new('n1'); + +$node->init(); + +# Disable autovacuum to guarantee VACUUM can remove rows / truncate relations +$node->append_conf( + 'postgresql.conf', qq[ +wal_level = 'replica' +autovacuum = off +]); + +$node->start(); + + +# Test: Replay replay of PRUNE records for a pre-existing, then dropped, +# relation + +$node->safe_psql( + 'postgres', qq[ +CREATE TABLE truncme(i int) WITH (fillfactor = 50); +INSERT INTO truncme SELECT generate_series(1, 1000); +UPDATE truncme SET i = 1; +CHECKPOINT; -- ensure relation exists at start of recovery +VACUUM truncme; -- generate prune records +DROP TABLE truncme; +]); + +$node->stop('immediate'); + +ok($node->start(), + 'replay of PRUNE records for a pre-existing, then dropped, relation'); + + +# Test: Replay of PRUNE records for a newly created, then dropped, relation + +$node->safe_psql( + 'postgres', qq[ +CREATE TABLE truncme(i int) WITH (fillfactor = 50); +INSERT INTO truncme SELECT generate_series(1, 1000); +UPDATE truncme SET i = 1; +VACUUM truncme; -- generate prune records +DROP TABLE truncme; +]); + +$node->stop('immediate'); + +ok($node->start(), + 'replay of PRUNE records for a newly created, then dropped, relation'); + + +# Test: Replay of PRUNE records affecting truncated block. With FPIs used for +# PRUNE. + +$node->safe_psql( + 'postgres', qq[ +CREATE TABLE truncme(i int) WITH (fillfactor = 50); +INSERT INTO truncme SELECT generate_series(1, 1000); +UPDATE truncme SET i = 1; +CHECKPOINT; -- generate FPIs +VACUUM truncme; -- generate prune records +TRUNCATE truncme; -- make blocks non-existing +INSERT INTO truncme SELECT generate_series(1, 10); +]); + +$node->stop('immediate'); + +ok($node->start(), + 'replay of PRUNE records affecting truncated block (FPIs)'); + +is($node->safe_psql('postgres', 'select count(*), sum(i) FROM truncme'), + '10|55', 'table contents as expected after recovery'); +$node->safe_psql('postgres', 'DROP TABLE truncme'); + + +# Test replay of PRUNE records for blocks that are later truncated. Without +# FPIs used for PRUNE. + +$node->safe_psql( + 'postgres', qq[ +CREATE TABLE truncme(i int) WITH (fillfactor = 50); +INSERT INTO truncme SELECT generate_series(1, 1000); +UPDATE truncme SET i = 1; +VACUUM truncme; -- generate prune records +TRUNCATE truncme; -- make blocks non-existing +INSERT INTO truncme SELECT generate_series(1, 10); +]); + +$node->stop('immediate'); + +ok($node->start(), + 'replay of PRUNE records affecting truncated block (no FPIs)'); + +is($node->safe_psql('postgres', 'select count(*), sum(i) FROM truncme'), + '10|55', 'table contents as expected after recovery'); +$node->safe_psql('postgres', 'DROP TABLE truncme'); + + +# Test: Replay of partial truncation via VACUUM + +$node->safe_psql( + 'postgres', qq[ +CREATE TABLE truncme(i int) WITH (fillfactor = 50); +INSERT INTO truncme SELECT generate_series(1, 1000); +UPDATE truncme SET i = i + 1; +-- ensure a mix of pre/post truncation rows +DELETE FROM truncme WHERE i > 500; + +VACUUM truncme; -- should truncate relation + +-- rows at TIDs that previously existed +INSERT INTO truncme SELECT generate_series(1000, 1010); +]); + +$node->stop('immediate'); + +ok($node->start(), 'replay of partial truncation via VACUUM'); + +is( $node->safe_psql( + 'postgres', 'select count(*), sum(i), min(i), max(i) FROM truncme'), + '510|136304|2|1010', + 'table contents as expected after recovery'); +$node->safe_psql('postgres', 'DROP TABLE truncme'); + + +done_testing(); |