Re: initdb's -c option behaves wrong way? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: initdb's -c option behaves wrong way?
Date
Msg-id 2040188.1705511127@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb's -c option behaves wrong way?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: initdb's -c option behaves wrong way?
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Hmm, how about raising an error if multiple options are given targetting
> the same GUC?

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: More new SQL/JSON item methods
Next
From: Robert Haas
Date:
Subject: Re: Emit fewer vacuum records by reaping removable tuples during pruning