| 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 15:49:25 |
| Message-ID: | Pine.LNX.4.21.0011251643380.1028-100000@peter.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> > I certainly don't like treating en_US specially, when in fact all locales
> > are affected by this.
>
> Well, my thought was that another locale, say en_FR, would be far more
> likely to be something that the system's user had explicitly chosen to
> use at some point,
IIRC, the default locale is chosen during the installation process of Red
Hat, so any locale is explicitly chosen. If Red Hat does not provide a
means to set the C locale as the default, that is Red Hat's fault. But
then it should also be Red Hat's job (and Red Hat's decision) to install
PostgreSQL in a certain way or other to account for that. Compiles from
source don't count here, those users enabled locale explicitly anyway.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim Mikheev | 2000-11-25 18:56:51 | Re: Are pg_control contents really variable-length? |
| Previous Message | Peter Eisentraut | 2000-11-25 15:43:14 | Re: OK, that's one LOCALE bug report too many... |