From 3279cef0727a0fd285f3f1f459a7094acff9f629 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Tue, 15 Feb 2022 11:55:52 +0200 Subject: [PATCH] Add more logging to new 028_pitr_timelines.pl test. The test has failed a couple of times on buildfarm member 'hoverfly'. It gets stuck waiting for the standby to archive 000000020000000000000003 WAL segment. I don't understand why, but with DEBUG1, we will get messages in the log whenever a segment is archived, which hopefully will give a clue the next time it happens. --- src/test/recovery/t/028_pitr_timelines.pl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/test/recovery/t/028_pitr_timelines.pl b/src/test/recovery/t/028_pitr_timelines.pl index 9a07786a53..c0b76fe37b 100644 --- a/src/test/recovery/t/028_pitr_timelines.pl +++ b/src/test/recovery/t/028_pitr_timelines.pl @@ -36,6 +36,7 @@ use File::Compare; # Initialize and start primary node with WAL archiving my $node_primary = PostgreSQL::Test::Cluster->new('primary'); $node_primary->init(has_archiving => 1, allows_streaming => 1); +$node_primary->append_conf('postgresql.conf', 'log_min_messages=debug1'); $node_primary->start; # Take a backup. @@ -69,6 +70,7 @@ $node_standby->init_from_backup( has_archiving => 1, has_restoring => 0); $node_standby->append_conf('postgresql.conf', 'archive_mode = always'); +$node_standby->append_conf('postgresql.conf', 'log_min_messages=debug1'); $node_standby->start; $node_primary->wait_for_catchup($node_standby); -- 2.39.5