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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: In initdb, don't bother trying max_connections = 10.
Date: 2018-03-08 16:26:58
Message-ID: E1etyNe-0004EE-6Z@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/6a0b30f0401a76b3a972e366ba30aa7e49ffbf87

Modified Files
--------------
src/bin/initdb/initdb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-03-08 16:35:26 pgsql: Revert "Temporarily instrument postgres_fdw test to look for sta
Previous Message Robert Haas 2018-03-07 22:18:07 pgsql: test_decoding: Remove unused #include directives.