Re: Overriding local encoding defaults

From: Bob McConnell <rmcconne(at)lightlink(dot)com>
To: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Overriding local encoding defaults
Date: 2010-10-17 22:01:36
Message-ID: 4CBB7240.7050109@lightlink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Tom Lane wrote:
> Bob McConnell <rmcconne(at)lightlink(dot)com> 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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message richard terry 2010-10-18 01:03:18 Dumping grants
Previous Message Tom Lane 2010-10-17 20:19:42 Re: Overriding local encoding defaults