Re: Server won't start with fallback setting by initdb. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Server won't start with fallback setting by initdb.
Date
Msg-id 20180307234330.GA1788@paquier.xyz
Whole thread Raw
In response to Re: Server won't start with fallback setting by initdb.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Server won't start with fallback setting by initdb.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Mar 07, 2018 at 06:39:32PM -0500, Tom Lane wrote:
> OK, seems like I'm on the short end of that vote.  I propose to push the
> GUC-crosschecking patch I posted yesterday, but not the default-value
> change, and instead push Kyotaro-san's initdb change.  Should we back-patch
> these things to v10 where the problem appeared?

I would vote for a backpatch.  If anybody happens to run initdb on v10
and gets max_connections to 10, that would immediately cause a failure.
We could also wait for sombody to actually complain about that, but a
bit of prevention does not hurt to ease future user experience on this
released version.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Server won't start with fallback setting by initdb.
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] [PATCH] Incremental sort