I run the following sql statements in linux and get the results:
postgres=# create table test_double(col1 float8);
CREATE TABLE
postgres=# insert into test_double values(1.7976931348623159E308);
INSERT 0 1
postgres=# select * from test_double;
   col1
----------
 Infinity
(1 row)

but in windows:
postgres=# create table test_double(col1 float8);
CREATE TABLE
postgres=# insert into test_double values(1.7976931348623159E308);
ERROR: 
"17976931348623159000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000"
is out of range for type double precision
postgres=# select * from test_double;
 col1
------
(0 rows)

This is a bug, the behavior in windows and linux is not the smae

I check the code and find that float8in exists a bug:
the strtod() function in linux dosen't set errno when dealing with 
1.7976931348623159E308 but in windows it does
How should we improve it?

Responses

• Re: bug in float8in() at 2008-04-02 08:58:59 from Zdenek Kotala
• Re: bug in float8in() at 2008-04-02 09:25:19 from Magnus Hagander

pgsql-hackers by date

Next:	From: James Mansion	Date: 2008-04-02 06:21:26
	Subject: notify with payload (pgkill, notify)
Previous:	From: Bruce Momjian	Date: 2008-04-02 03:06:26
	Subject: Re: [GENERAL] SHA1 on postgres 8.3