diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2022-02-15 11:55:52 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2022-02-15 11:55:52 +0200 |
| commit | 3279cef0727a0fd285f3f1f459a7094acff9f629 (patch) | |
| tree | 4156dceb6723ae34f4f609394985ae14b7bc5122 /src | |
| parent | 797129e5910144a2a937b88e145874a15b83578a (diff) | |
| download | postgresql-3279cef0727a0fd285f3f1f459a7094acff9f629.tar.gz postgresql-3279cef0727a0fd285f3f1f459a7094acff9f629.zip | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/test/recovery/t/028_pitr_timelines.pl | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/test/recovery/t/028_pitr_timelines.pl b/src/test/recovery/t/028_pitr_timelines.pl index 9a07786a539..c0b76fe37b2 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); |