diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-10-01 10:59:20 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-10-01 10:59:20 -0400 |
| commit | ad4cf31ec0cdd474798335e5412341cf11ed1d45 (patch) | |
| tree | a64d1f9c5391d9eab81603d30bd157e40bdaad92 /src/test/perl/PostgresNode.pm | |
| parent | 17fc1c729fc2220fee1ec125ff63d2f7ba6f466e (diff) | |
Put back explicit setting of replication values within TAP tests.
Commit 151c0c5f7 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/723911.1601417626@sss.pgh.pa.us
Diffstat (limited to 'src/test/perl/PostgresNode.pm')
| -rw-r--r-- | src/test/perl/PostgresNode.pm | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/test/perl/PostgresNode.pm b/src/test/perl/PostgresNode.pm index 00fe082fe4e..e69878c98ee 100644 --- a/src/test/perl/PostgresNode.pm +++ b/src/test/perl/PostgresNode.pm @@ -477,12 +477,15 @@ sub init { print $conf "wal_level = replica\n"; } - print $conf "max_wal_size = 128MB\n"; + print $conf "max_wal_senders = 10\n"; + print $conf "max_replication_slots = 10\n"; print $conf "wal_log_hints = on\n"; print $conf "hot_standby = on\n"; # conservative settings to ensure we can run multiple postmasters: print $conf "shared_buffers = 1MB\n"; print $conf "max_connections = 20\n"; + # limit disk space consumption, too: + print $conf "max_wal_size = 128MB\n"; } else { |