Re: initdb's -c option behaves wrong way?

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: initdb's -c option behaves wrong way?
Дата
Msg-id 5DFF3111-8ECA-4EF5-B614-9A4C9FAB29BC@yesql.se
обсуждение исходный текст
Ответ на Re: initdb's -c option behaves wrong way?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: initdb's -c option behaves wrong way?  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
> On 17 Jan 2024, at 18:05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

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




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Matthias van de Meent
Дата:
Сообщение: Re: cleanup patches for incremental backup
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: More new SQL/JSON item methods