Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1eqNlV-0002h0-N7
	for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Feb 2018 18:44:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1eqNlU-0003kk-VA
	for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Feb 2018 18:44:44 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1eqNhx-0007Lk-Fg
	for pgsql-bugs@lists.postgresql.org; Mon, 26 Feb 2018 18:41:05 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1eqNhu-00006M-Mp; Mon, 26 Feb 2018 18:41:04 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w1QIevRX030448;
	Mon, 26 Feb 2018 13:40:57 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonathan Allen <jallen@americansavingslife.com>
cc: Michael Meskes <meskes@postgresql.org>,
        Andrew Gierth <andrew@tao11.riddles.org.uk>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
In-reply-to: 
 <BN6PR17MB1330F6AD0F67C1D34D695CB7DAC10@BN6PR17MB1330.namprd17.prod.outlook.com>
References: <151935568942.1461.14623890240535309745@wrigleys.postgresql.org>
 <1519483386.2654.291.camel@postgresql.org>
 <877er2nr8c.fsf@news-spur.riddles.org.uk>
 <1519501766.2510.13.camel@postgresql.org> <20053.1519502594@sss.pgh.pa.us>
 <20439.1519503130@sss.pgh.pa.us>
 <BN6PR17MB1330F6AD0F67C1D34D695CB7DAC10@BN6PR17MB1330.namprd17.prod.outlook.com>
Comments: In-reply-to Jonathan Allen <jallen@americansavingslife.com>
	message dated "Mon, 26 Feb 2018 18:28:12 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30446.1519670457.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Feb 2018 13:40:57 -0500
Message-ID: <30447.1519670457@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

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 working in the next release of pos=
tgres.  I agree, all that's missing is the #define HAVE_LONG_LONG_INT 1 li=
ne. :)

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