Skip site navigation (1) Skip section navigation (2)

Re: Day and month name localization uses wrong

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:57:45
Message-ID: 200611271957.kARJvj903169@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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
> 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.

Agreed.  There is no reported failure in the field, and it is a
preventative fix.

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-11-27 20:11:18
Subject: Re: PrivateRefCount (for 8.3)
Previous:From: Bruce MomjianDate: 2006-11-27 19:56:35
Subject: Re: Potential to_char localization bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group