Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Subject: Re: initdb's -c option behaves wrong way?
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <2040188.1705511127@sss.pgh.pa.us>
Date: Wed, 17 Jan 2024 20:30:48 +0100
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
 pgsql-hackers@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DFF3111-8ECA-4EF5-B614-9A4C9FAB29BC@yesql.se>
References: <202401171615.uzdmkozzvo6x@alvherre.pgsql>
 <2040188.1705511127@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/5DFF3111-8ECA-4EF5-B614-9A4C9FAB29BC%40yesql.se>
Precedence: bulk

> On 17 Jan 2024, at 18:05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>> Hmm, how about raising an error if multiple options are given =
targetting
>> the same GUC?
>=20
> I don't see any reason to do that.  The underlying configuration
> files don't complain about duplicate entries, they just take the
> last setting.

Agreed, I think the patch as it stands now where it replaces case =
insensitive,
while keeping the original casing, is the best path forward.  The issue =
exist
in 16 as well so I propose a backpatch to there.

--
Daniel Gustafsson