Re: suggest to rename enable_incrementalsort

Поиск
Список
Период
Сортировка
От Tomas Vondra
Тема Re: suggest to rename enable_incrementalsort
Дата
Msg-id 20200621112159.qtgedtrqw2c47pm4@development
обсуждение исходный текст
Ответ на Re: suggest to rename enable_incrementalsort  (Julien Rouhaud <rjuju123@gmail.com>)
Ответы Re: suggest to rename enable_incrementalsort  (David Rowley <dgrowleyml@gmail.com>)
Re: suggest to rename enable_incrementalsort  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Sun, Jun 21, 2020 at 09:05:32AM +0200, Julien Rouhaud wrote:
>On Sun, Jun 21, 2020 at 8:26 AM Peter Eisentraut
><peter.eisentraut@2ndquadrant.com> wrote:
>>
>> I suggest to rename enable_incrementalsort to enable_incremental_sort.
>> This is obviously more readable and also how we have named recently
>> added multiword planner parameters.
>>
>> See attached patch.
>
>+1, this is a way better name (and patch LGTM on REL_13_STABLE).
>

The reason why I kept the single-word variant is consistency with other
GUCs that affect planning, like enable_indexscan, enable_hashjoin and
many others.

That being said, I'm not particularly attached this choice, so if you
think this is better I'm OK with it.


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: pg_regress cleans up tablespace twice.
Следующее
От: Josef Šimánek
Дата:
Сообщение: Re: [PATCH] Initial progress reporting for COPY command