Right now I'm using a custom build of ecpg to enable Bigint support, but it would suuuuure be nice to have that working
inthe next release of postgres. I agree, all that's missing is the #define HAVE_LONG_LONG_INT 1 line. :)
-Jonathan
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Saturday, February 24, 2018 1:12 PM
To: Michael Meskes <meskes@postgresql.org>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>; Jonathan Allen <jallen@americansavingslife.com>;
pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
I wrote:
> Michael Meskes <meskes@postgresql.org> writes:
>> Right, but it is missing in pg_config.h, too, right?
> No, it does get defined on Unix builds (if appropriate), both in
> pg_config.h and ecpg_config.h.
Oh, wait, now I see what you meant: there is no stanza like
#if (_MSC_VER > 1200)
#define HAVE_LONG_LONG_INT 1
#endif
in pg_config.h.win32. I agree that there should be. As I said, none of the core backend cares at the moment ... but
someday,that discrepancy is going to bite us.
regards, tom lane