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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Allen <jallen(at)americansavingslife(dot)com>
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" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date: 2018-02-27 21:48:21
Message-ID: 27949.1519768101@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jonathan Allen 2018-02-27 22:59:18 RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Previous Message David G. Johnston 2018-02-27 18:48:49 Re: pgAdmin Development Team || pgAdmin (PostgreSQL Management tool) 4 ||Version 2.0 || EULA questionnaire