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

Re: NaN/Inf fix for ECPG

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rémi Zara <remi_zara(at)mac(dot)com>
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-26 16:11:31
Message-ID: 28428.1267200691@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
=?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().

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-26 16:14:01
Subject: Re: NaN/Inf fix for ECPG
Previous:From: Tom LaneDate: 2010-02-26 16:05:10
Subject: ecpg tests broken by pgindent run

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