Re: Overriding local encoding defaults

Поиск
Список
Период
Сортировка
Искать
От
Bob McConnell
Тема
Re: Overriding local encoding defaults
Дата
Msg-id
4CBB7240.7050109@lightlink.com
Ответ на
Список
Дерево обсуждения
Overriding local encoding defaults Bob McConnell <rmcconne@lightlink.com>
Re: Overriding local encoding defaults Leif Biberg Kristensen <leif@solumslekt.org>
Re: Overriding local encoding defaults Tom Lane <tgl@sss.pgh.pa.us>
Re: Overriding local encoding defaults Bob McConnell <rmcconne@lightlink.com>
Re: Overriding local encoding defaults Tom Lane <tgl@sss.pgh.pa.us>
Re: Overriding local encoding defaults Bob McConnell <rmcconne@lightlink.com>
Re: Overriding local encoding defaults Lukasz Brodziak <lukasz.brodziak@gmail.com>
Re: Overriding local encoding defaults jr <jorg.raskowski@tailorware.org.uk>
Re: Overriding local encoding defaults Bob McConnell <rmcconne@lightlink.com>
Tom Lane wrote:
> Bob McConnell  writes:
>> I still don't understand why a server process should care about the 
>> local console. Are there any plans to fix that?
> 
> No, because it's not broken.  Where else should initdb get the default
> locale setting, if not from the environment it's invoked in?

Something that critical should never be left to a default. It should be 
explicitly required in the command line and ignore all of the local 
settings. In this case, the local settings are irrelevant anyway. The 
console will never be used to access the DB on a headless server.

But what I think is broken is that the command line argument is blocked 
by the local settings. When the command line says to use UTF-8, it 
should override any and all local settings. They become superfluous.

Bob McConnell
N2SPP

В списке pgsql-novice по дате отправления
От: Tom Lane
Дата:
От: richard terry
Дата:
Сообщение: Dumping grants
FAQ