Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date
Msg-id 30447.1519670457@sss.pgh.pa.us
Whole thread Raw
In response to RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Jonathan Allen <jallen@americansavingslife.com>)
Responses Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Jonathan Allen <jallen@americansavingslife.com> writes:
> Right now I'm using a custom build of ecpg to enable Bigint support, but it would suuuuure be nice to have that
workingin the next release of postgres.  I agree, all that's missing is the #define HAVE_LONG_LONG_INT 1 line. :) 

I'm afraid to push this in today, because today is a release wrap day,
and there's no time to recover if it turns out that we tickle some
portability issue.  But I think we should fix it as soon as the release
dust settles.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Michael Aiello
Date:
Subject: RE: BUG #15091: to_number() returns incorrect value
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #15091: to_number() returns incorrect value