Re: Current CVS has strange parser for float type

From: Teodor Sigaev <teodor(at)stack(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Current CVS has strange parser for float type
Date: 2002-10-18 07:34:36
Message-ID: 3DAFB98C.70003@stack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

wow=# show lc_numeric;
lc_numeric
--------------
ru_RU.KOI8-R
(1 row)

wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
wow=# set lc_numeric = 'C';
SET
wow=# select 5.3::float;
float8
--------
5.3
(1 row)

It's locale.

Tom Lane wrote:
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
>
>>On Thu, 2002-10-17 at 23:34, Teodor Sigaev wrote:
>>
>>>wow=# select 5.3::float;
>>>ERROR: Bad float8 input format '5.3'
>>
>>Could it be something with locales ?
>
>
> Oooh, bingo! On HPUX:
>
> regression=# select 5.3::float;
> float8
> --------
> 5.3
> (1 row)
>
> regression=# set lc_numeric = 'de_DE.iso88591';
> SET
> regression=# select 5.3::float;
> ERROR: Bad float8 input format '5.3'
>
> I think this is a consequence of the changes made a little while back
> (by Peter IIRC?) in locale handling. It used to be that we deliberately
> did *not* allow any LC_ setting except LC_MESSAGES to actually take
> effect globally in the backend, and this sort of problem is exactly
> why. I think we need to revert some aspects of that change.
>
> Bruce, this is a "must fix" open item ...
>
> regards, tom lane
>

--
Teodor Sigaev
teodor(at)stack(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mats Lofkvist 2002-10-18 09:21:03 Re: Analysis of ganged WAL writes
Previous Message Teodor Sigaev 2002-10-18 07:31:41 Re: Current CVS has strange parser for float type