| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Day and month name localization uses wrong |
| Date: | 2006-11-27 19:55:20 |
| Message-ID: | 23076.1164657320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Actually, now that I look at it, *most* of the variants of to_char,
>> to_number, and friends have been broken on this score since day one.
>> There's been a dependency on LC_NUMERIC for the numeric variants all
>> along, but they're marked immutable :-(
> Where are we on this?
In the past our practice has been to go ahead and back-patch such
changes, eg
http://archives.postgresql.org/pgsql-committers/2003-04/msg00095.php
Obviously we can't force initdb in the back branches, but we can and
should get the entries right for future installations.
I think the only interesting question is whether we should force initdb
in HEAD. I'd prefer not to since we're past RC1. This is a pretty
minor bug really, and I don't think it justifies forcing a dump/reload
cycle on people testing RC1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-11-27 19:56:35 | Re: Potential to_char localization bug |
| Previous Message | Dennis Bjorklund | 2006-11-27 19:47:27 | Re: Potential to_char localization bug |