| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Jorge Godoy <jgodoy(at)gmail(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] wrong behavior using to_char() |
| Date: | 2007-02-09 04:29:11 |
| Message-ID: | 14701.1170995351@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Ultimately, the result was that glibc was wrong in its locale settings,
> and there was a suggestion to use defaults only when using the C locale.
> However, I am worried there are too many locales in the field that only
> define some of the locale setting, so doing defaults only for the C
> locale might not work.
> The minimal patch I wrote (attached), suppresses the default for the
> thousands separator only if is is the same as the decimal separator. I
> think this is the only area where the default could potentially match
> the locale setting for another field.
Should we really go introducing strange misbehaviors into our code to
work around an admitted glibc bug?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Flater | 2007-02-09 16:06:06 | BUG #2983: Nonsense error: "Table has type interval, but query expects interval" |
| Previous Message | Bruce Momjian | 2007-02-09 04:21:39 | Re: [BUGS] wrong behavior using to_char() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Marcellino | 2007-02-09 05:05:04 | Feature: POSIX Shared memory support, round 2 |
| Previous Message | Bruce Momjian | 2007-02-09 04:21:39 | Re: [BUGS] wrong behavior using to_char() |