diff options
author | Michael Paquier | 2025-02-07 00:42:31 +0000 |
---|---|---|
committer | Michael Paquier | 2025-02-07 00:42:31 +0000 |
commit | 428fadb7e97e3c95180d75dea73de99c491a9f65 (patch) | |
tree | fbefb93fb1120759915ed9d64d8cc2ef3599449a /src/test/recovery | |
parent | 401a6956fa69c9202cbc14c09ba8a9c430b90cac (diff) |
Move SQL tests of pg_stat_io for WAL data to recovery test 029_stats_restart
Three tests in the main regression test suite are proving to not be
portable across multiple runs on a deployed cluster as stats of
pg_stat_io are reset. Problems happen for tests on:
- Writes of WAL in the init context, when creating a WAL segment.
- Syncs of WAL in the init context, when creating a WAL segment.
- Reads of WAL in the normal context, requiring a WAL record to be read.
For a `make check`, this could rely on the checkpoint record read by the
startup process when starting the cluster, something that is not going
to work for a deployed node.
Two of the three tests are moved to the recovery TAP test
029_stats_restart, where we already check the consistency of stats
data. The test for syncs is dropped as TAP can run with fsync=off. The
other two are checked with some data from a freshly-initialized cluster.
Per discussion with Tom Lane, Bertrand Drouvot and Nazir Bilal Yavuz.
Discussion: https://postgr.es/m/[email protected]
Diffstat (limited to 'src/test/recovery')
-rw-r--r-- | src/test/recovery/t/029_stats_restart.pl | 34 |
1 files changed, 33 insertions, 1 deletions
diff --git a/src/test/recovery/t/029_stats_restart.pl b/src/test/recovery/t/029_stats_restart.pl index be626059177..021e2bf361f 100644 --- a/src/test/recovery/t/029_stats_restart.pl +++ b/src/test/recovery/t/029_stats_restart.pl @@ -18,6 +18,21 @@ $node->start; my $connect_db = 'postgres'; my $db_under_test = 'test'; +my $sect = "startup"; + +# Check some WAL statistics after a fresh startup. The startup process +# should have done WAL reads, and initialization some WAL writes. +my $standalone_io_stats = io_stats('init', 'wal', 'standalone backend'); +my $startup_io_stats = io_stats('normal', 'wal', 'startup'); +cmp_ok( + '0', '<', + $standalone_io_stats->{writes}, + "$sect: increased standalone backend IO writes"); +cmp_ok( + '0', '<', + $startup_io_stats->{reads}, + "$sect: increased startup IO reads"); + # create test objects $node->safe_psql($connect_db, "CREATE DATABASE $db_under_test"); $node->safe_psql($db_under_test, @@ -39,7 +54,7 @@ my $tableoid = $node->safe_psql($db_under_test, trigger_funcrel_stat(); # verify stats objects exist -my $sect = "initial"; +$sect = "initial"; is(have_stats('database', $dboid, 0), 't', "$sect: db stats do exist"); is(have_stats('function', $dboid, $funcoid), 't', "$sect: function stats do exist"); @@ -342,3 +357,20 @@ sub wal_stats return \%results; } + +sub io_stats +{ + my ($context, $object, $backend_type) = @_; + my %results; + + $results{writes} = $node->safe_psql( + $connect_db, qq{SELECT writes FROM pg_stat_io + WHERE context = '$context' AND object = '$object' AND + backend_type = '$backend_type'}); + $results{reads} = $node->safe_psql( + $connect_db, qq{SELECT reads FROM pg_stat_io + WHERE context = '$context' AND object = '$object' AND + backend_type = '$backend_type'}); + + return \%results; +} |