Re: Locale support is now on by default - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Locale support is now on by default
Date
Msg-id Pine.LNX.4.30.0204031126330.684-100000@peter.localdomain
Whole thread Raw
In response to Re: Locale support is now on by default  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> > initdb --lc-collate, initdb --locale, LC_ALL, LC_COLLATE, LANG
> > initdb --no-locale is the same as initdb --locale=C, for convenience.
>
> I'm confused; what is the default behavior if you don't give any
> switches to initdb?

Whatever is set in the environment -- which boils down to LC_ALL,
LC_COLLATE, LANG.

> It might be that Bruce's recent changes to elog levels allow a graceful
> compromise about backend messages during initdb.  I haven't looked, but
> maybe initdb could run the backend with message level one notch higher
> than LOG to suppress all the normal-case messages without masking not-
> so-normal cases.

I'll look.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Odd psql \i behaviour
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Re : Solaris Performance - Profiling (Solved)