Skip to content

Commit 3279cef

Browse files
committed
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.
1 parent 797129e commit 3279cef

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

src/test/recovery/t/028_pitr_timelines.pl

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@
3636
# Initialize and start primary node with WAL archiving
3737
my $node_primary = PostgreSQL::Test::Cluster->new('primary');
3838
$node_primary->init(has_archiving => 1, allows_streaming => 1);
39+
$node_primary->append_conf('postgresql.conf', 'log_min_messages=debug1');
3940
$node_primary->start;
4041

4142
# Take a backup.
@@ -69,6 +70,7 @@
6970
has_archiving => 1,
7071
has_restoring => 0);
7172
$node_standby->append_conf('postgresql.conf', 'archive_mode = always');
73+
$node_standby->append_conf('postgresql.conf', 'log_min_messages=debug1');
7274
$node_standby->start;
7375
$node_primary->wait_for_catchup($node_standby);
7476

0 commit comments

Comments
 (0)