Re: NaN/Inf fix for ECPG - Mailing list pgsql-hackers

From Tom Lane
Subject Re: NaN/Inf fix for ECPG
Date
Msg-id 28484.1267200841@sss.pgh.pa.us
Whole thread Raw
In response to Re: NaN/Inf fix for ECPG  (Michael Meskes <meskes@postgresql.org>)
Responses Re: NaN/Inf fix for ECPG  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Michael Meskes <meskes@postgresql.org> writes:
> On Fri, Feb 26, 2010 at 12:12:10PM +0100, Boszormenyi Zoltan wrote:
>> Michael, can we try to install the first two patches?

> If I understood the rest of the thread correctly this is not needed anymore,
> right?

I think it would be a good idea, just to have all that code using
identical #includes.  R�mi's problem may be a platform bug rather
than something we can fix ourselves, but I think that making sure that
ecpg uses the exact same coding that's been proven in the backend
will forestall problems on other platforms.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: NaN/Inf fix for ECPG
Next
From: Tom Lane
Date:
Subject: Re: Avoiding bad prepared-statement plans.