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 ) id 1eqn6s-0008EK-Pp for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Feb 2018 21:48:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eqn6q-0003ZD-Ew for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Feb 2018 21:48:28 +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 ) id 1eqn6q-0003Yz-8g for pgsql-bugs@lists.postgresql.org; Tue, 27 Feb 2018 21:48:28 +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 ) id 1eqn6n-0005KI-R3; Tue, 27 Feb 2018 21:48:27 +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 w1RLmLea027950; Tue, 27 Feb 2018 16:48:21 -0500 From: Tom Lane To: Jonathan Allen cc: Michael Meskes , Andrew Gierth , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT In-reply-to: <30447.1519670457@sss.pgh.pa.us> 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> <30447.1519670457@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 26 Feb 2018 13:40:57 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27948.1519768101.1@sss.pgh.pa.us> Date: Tue, 27 Feb 2018 16:48:21 -0500 Message-ID: <27949.1519768101@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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