RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT

I saw the release of v10.4 today and was very excited to try using the official version of ecpg, but unfortunately I'm getting the same "unsupported type "long long" on line x" error. SQL State: YE000, SQL Code: -200.

...did this fix not make it into the May release?

I guess I'm back to my custom build again. ☹

-Jonathan

-----Original Message-----
From: Jonathan Allen <jallen(at)americansavingslife(dot)com>
Sent: Tuesday, February 27, 2018 3:59 PM
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>; Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT

[This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

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 - what am I complaining about, right? I very much look forward to an official build of ecpg that properly handles Bigint right out of the box.

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

-Jonathan

-----Original Message-----

From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]

Sent: Tuesday, February 27, 2018 2:48 PM

To: Jonathan Allen <jallen(at)americansavingslife(dot)com<mailto:jallen(at)americansavingslife(dot)com>>

Cc: Michael Meskes <meskes(at)postgresql(dot)org<mailto:meskes(at)postgresql(dot)org>>; Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk<mailto:andrew(at)tao11(dot)riddles(dot)org(dot)uk>>; pgsql-bugs(at)lists(dot)postgresql(dot)org<mailto:pgsql-bugs(at)lists(dot)postgresql(dot)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