Re: initdb --no-locale=C doesn't work as specified when the environment is not C

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: initdb --no-locale=C doesn't work as specified when the environment is not C
Дата
Msg-id 2678842.1704928563@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: initdb --no-locale=C doesn't work as specified when the environment is not C  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: initdb --no-locale=C doesn't work as specified when the environment is not C  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-hackers
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> It seems somewhat intentional that only lc_messages references the
> environment at boot time. On the other hand, previously, in the
> absence of a specified locale, initdb would embed the environmental
> value in the configuration file, as it seems to be documented. Given
> that initdb is always used for cluster creation, it's unlikey that
> systems depend on this boot-time default for their operation.

Yeah, after further reflection there doesn't seem to be a lot of value
in leaving these entries commented-out, even in the cases where that's
technically correct.  Let's just go back to the old behavior of always
uncommenting them; that stood for years without complaints.  So I
committed your latest patch as-is.

> By the way, the lines around lc_* in the sample file seem to have
> somewhat inconsistent indentations. Wouldnt' it be preferable to fix
> this? (The attached doesn't that.)

They look all right if you assume the tab width is 8, which seems to
be what is used elsewhere in the file.  I think there's been some
prior discussion about whether to ban use of tabs at all in these
sample files, so as to reduce confusion about how wide the tabs are.
But I'm not touching that question today.

            regards, tom lane



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

Предыдущее
От: "Daniel Verite"
Дата:
Сообщение: Re: Built-in CTYPE provider
Следующее
От: Melanie Plageman
Дата:
Сообщение: Re: Show WAL write and fsync stats in pg_stat_io