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

Re: NaN/Inf fix for ECPG

From: Rémi Zara <remi_zara(at)mac(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NaN/Inf fix for ECPG
Date: 2010-02-27 13:40:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Le 26 févr. 2010 à 17:11, Tom Lane a écrit :

> =?iso-8859-1?Q?R=E9mi_Zara?= <remi_zara(at)mac(dot)com> writes:
>> I've tried patch 1 and 2, but they do not work. The fact is that the code is not used in the backend, because strtod("NaN", endptr) works. (isnan(strtod("NaN", endptr)) is true).
> Hmm.  So what do you get from
> 	SELECT 'nan'::numeric::float8;
> on that machine?  That should exercise the backend's version of
> get_float8_nan().

regression=# select 'nan'::numeric::float8;
(1 row)

So it is indeed the same behavior. Maybe that should be added to the regression tests.
So what's the best way to workaround the bug in NetBSD/mips ? (nan(""), (0.0/0.0), strtod("nan", null) ?)


Rémi Zara

In response to


pgsql-hackers by date

Next:From: Dickson S. GuedesDate: 2010-02-27 14:02:15
Subject: Re: caracara failing to bind to localhost?
Previous:From: Mark KirkwoodDate: 2010-02-27 10:40:24
Subject: Re: Lock Wait Statistics (next commitfest)

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