From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: jallen@americansavingslife.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date: Sat, 24 Feb 2018 14:21:23 -0500
Message-ID: <16785.1519500083@sss.pgh.pa.us> (raw)
In-Reply-To: <877er2nr8c.fsf@news-spur.riddles.org.uk>
References: <151935568942.1461.14623890240535309745@wrigleys.postgresql.org>
<1519483386.2654.291.camel@postgresql.org>
<877er2nr8c.fsf@news-spur.riddles.org.uk>
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> Solution.pm has this:
> #if (_MSC_VER > 1200)
> #define HAVE_LONG_LONG_INT_64 1
> #define ENABLE_THREAD_SAFETY 1
> #endif
> from which HAVE_LONG_LONG_INT seems to be suspiciously missing?
I remember noticing that discrepancy recently when I was chasing something
else about int64 support. It certainly looks wrong, but not being much of
an ecpg user I was hesitant to touch it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@tao11.riddles.org.uk, meskes@postgresql.org, jallen@americansavingslife.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
In-Reply-To: <16785.1519500083@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox