Re: Locale support is now on by default

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Locale support is now on by default
Date: 2002-04-03 16:28:16
Message-ID: Pine.LNX.4.30.0204031126330.684-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2002-04-03 16:32:57 Re: [GENERAL] Re : Solaris Performance - Profiling (Solved)
Previous Message Peter Eisentraut 2002-04-03 16:25:39 Re: Odd psql \i behaviour