From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: OK, that's one LOCALE bug report too many... |
Date: | 2000-11-25 01:36:46 |
Message-ID: | Pine.LNX.4.21.0011250210240.791-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2000-11-25 01:55:16 | Re: OK, that's one LOCALE bug report too many... |
Previous Message | Tom Lane | 2000-11-25 01:36:23 | Re: OK, that's one LOCALE bug report too many... |