Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 26f4c14

Browse files
committed
Put back explicit setting of replication values within TAP tests.
Commit 151c0c5 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than assuming that max_wal_senders=10 will prevail if we say nothing, set it explicitly. Set max_replication_slots=10 explicitly too, just to be safe. Back-patch to v10, like the previous patch. Discussion: https://postgr.es/m/[email protected]
1 parent 3ae6ed9 commit 26f4c14

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/test/perl/PostgresNode.pm

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -443,13 +443,16 @@ sub init
443443
{
444444
print $conf "wal_level = replica\n";
445445
}
446+
print $conf "max_wal_senders = 10\n";
447+
print $conf "max_replication_slots = 10\n";
446448
print $conf "wal_keep_segments = 20\n";
447-
print $conf "max_wal_size = 128MB\n";
448449
print $conf "wal_log_hints = on\n";
449450
print $conf "hot_standby = on\n";
450451
# conservative settings to ensure we can run multiple postmasters:
451452
print $conf "shared_buffers = 1MB\n";
452453
print $conf "max_connections = 20\n";
454+
# limit disk space consumption, too:
455+
print $conf "max_wal_size = 128MB\n";
453456
}
454457
else
455458
{

0 commit comments

Comments
 (0)