In initdb, don't bother trying max_connections = 10.

The server won't actually start with that setting anymore, not since
we raised the default max_wal_senders to 10.  Per discussion, we don't
wish to back down on that default, so instead raise the effective floor
for max_connections (to 20).  It's still possible to configure a smaller
setting manually, but initdb won't set it that way.

Since that change happened in v10, back-patch to v10.

Kyotaro Horiguchi

Discussion: https://postgr.es/m/20180209.170823.42008365.horiguchi.kyotaro@lab.ntt.co.jp

diff --git a/src/bin/initdb/initdb.c b/src/bin/initdb/initdb.c
index 7303bbe8923734a656ca1ac16b3afd52fccab288..9a5bdb080dd013bf883f7f6d52e8dc297152eef0 100644 (file)
--- a/src/bin/initdb/initdb.c
+++ b/src/bin/initdb/initdb.c
@@ -912,7 +912,7 @@ test_config_settings(void)
 #define MIN_BUFS_FOR_CONNS(nconns)     ((nconns) * 10)
 
        static const int trial_conns[] = {
-               100, 50, 40, 30, 20, 10
+               100, 50, 40, 30, 20
        };
        static const int trial_bufs[] = {
                16384, 8192, 4096, 3584, 3072, 2560, 2048, 1536,