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 | 6731f1ef19fdf912cfbf2686a4d344a022b7704b (patch) | |
| tree | a41174e5f326692c6972bd242e8cccd49de34665 /src/backend/access/gist/gistxlog.c | |
| parent | 3c85489ec9cd08ce43976afa75f613f939635cb9 (diff) | |
| download | postgresql-6731f1ef19fdf912cfbf2686a4d344a022b7704b.tar.gz postgresql-6731f1ef19fdf912cfbf2686a4d344a022b7704b.zip | |
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/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions