Re: [BUGS] wrong behavior using to_char() - Mailing list pgsql-patches

From Tom Lane
Subject Re: [BUGS] wrong behavior using to_char()
Date
Msg-id 14701.1170995351@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] wrong behavior using to_char()  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [BUGS] wrong behavior using to_char()
List pgsql-patches
Bruce Momjian <bruce@momjian.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

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] wrong behavior using to_char()
Next
From: Chris Marcellino
Date:
Subject: Feature: POSIX Shared memory support, round 2