]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Put back explicit setting of replication values within TAP tests.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Oct 2020 14:59:20 +0000 (10:59 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Oct 2020 14:59:20 +0000 (10:59 -0400)
commit6731f1ef19fdf912cfbf2686a4d344a022b7704b
treea41174e5f326692c6972bd242e8cccd49de34665
parent3c85489ec9cd08ce43976afa75f613f939635cb9
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
src/test/perl/PostgresNode.pm