> Christopher Kings-Lynne wrote:
>> > When this new behavior was introduced, and I migrated our databases to
>> > the new PgSQL version (dump/restore), the locale of all my databases
>> > were silently changed from C to US_en. This broke one application in a
>> > very subtle way because of slightly different sort behavior in the
>> > different locale. Tracking it down was quite tricky.
>> >
>> > PgSQL was just a little too helpful in this case.
>>
>> Seems pretty nasty thing to do.  I would so vote for making -E and -W
>> and --locate required flags to initdb.  Oh the amount of time I've spent
>> with people in IRC..
>
> What about folks who don't use locales?

This has bitten me a couple times. In what version did it change?

My feeling, and I'd like to see what everyone else thinks, is that if you
do not specify a locale, you get "C."

That way things work as you'd expect in most cases.

In response to

• Re: Default Locale in initdb at 2004-06-03 01:30:02 from Bruce Momjian

Responses

• Re: Default Locale in initdb at 2004-06-03 01:51:43 from Christopher Kings-Lynne

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2004-06-03 02:08:07
	Subject: pgsql-server: Adjust our timezone library to use pg_time_t (typedef'd as
Previous:	From: Christopher Kings-Lynne	Date: 2004-06-03 01:51:43
	Subject: Re: Default Locale in initdb