Re: OK, that's one LOCALE bug report too many... - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: OK, that's one LOCALE bug report too many...
Date
Msg-id Pine.LNX.4.21.0011250210240.791-100000@peter.localdomain
Whole thread Raw
In response to Re: OK, that's one LOCALE bug report too many...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: OK, that's one LOCALE bug report too many...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> Possible compromise: let initdb accept en_US, but have it spit out a
> warning message:
> 
> NOTICE: initializing database with en_US collation order.
> If you're not certain that's what you want, then it's probably not what
> you want.  We recommend you set LC_COLLATE to "C" and re-initdb.
> For more information see <appropriate place in admin guide>

I certainly don't like treating en_US specially, when in fact all locales
are affected by this.  You could print a general notice that the database
system will be initialized with a (non-C, non-POSIX) locale and that this
may/will affect the performance in certain cases.  Maybe a
--disable-locale switch to initdb as well?

But IMHO we're not in the business of nitpicking or telling people how to
write, install, or use their operating systems when the issue is not a
show-stopper type, but really an aesthetics/convenience issue.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: OK, that's one LOCALE bug report too many...
Next
From: Tom Lane
Date:
Subject: Re: OK, that's one LOCALE bug report too many...