Tom Lane wrote:
> 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
> 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.
Agreed. There is no reported failure in the field, and it is a
Bruce Momjian bruce(at)momjian(dot)us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2006-11-27 20:11:18|
|Subject: Re: PrivateRefCount (for 8.3)|
|Previous:||From: Bruce Momjian||Date: 2006-11-27 19:56:35|
|Subject: Re: Potential to_char localization bug|