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

From Jonathan Allen
Subject RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date
Msg-id BN6PR17MB133047E15B85612606D818DADAC00@BN6PR17MB1330.namprd17.prod.outlook.com
Whole thread Raw
In response to Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
List pgsql-bugs
Thank you!  Thank you so very much.  Using my own private build of ecpg until May will be a bit of a pain but hey -
whatam I complaining about, right?  I very much look forward to an official build of ecpg that properly handles Bigint
rightout of the box. 

Thanks again for getting that worked out and released into the build pipeline,

-Jonathan

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, February 27, 2018 2:48 PM
To: Jonathan Allen <jallen@americansavingslife.com>
Cc: Michael Meskes <meskes@postgresql.org>; Andrew Gierth <andrew@tao11.riddles.org.uk>;
pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT

I wrote:
> 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.

Pushed now.  Barring buildfarm complaints, it'll be in our May releases.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Next
From: pkashimalla
Date:
Subject: How to avoid trailing zero (after decimal point) for numeric typecolumn