From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix two places that thought Windows64 is indicated by WIN64 macr |
Date: | 2016-04-11 23:37:09 |
Message-ID: | E1aplOH-0002He-Rs@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix two places that thought Windows64 is indicated by WIN64 macro.
Everyplace else thinks it's _WIN64, so make these places fall in line.
The pg_regress.c usage is not going to result in any change in behavior,
only suppressing (or not) a compiler warning about downcasting HANDLEs.
So there seems no need for back-patching there.
The libpq/win32.mak usage might represent an actual bug, if anyone were
using this script to build for Windows64, which perhaps nobody is.
Given the lack of field complaints, no back-patch here either.
pg_regress.c problem found by Christian Ullrich, the other by me.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/b0e40d189325dc7a54d2546245e766f8c47a7c8d
Modified Files
--------------
src/interfaces/libpq/win32.mak | 2 +-
src/test/regress/pg_regress.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-04-12 00:07:26 | pgsql: Fix _SPI_execute_plan() for CREATE TABLE IF NOT EXISTS foo AS .. |
Previous Message | Tom Lane | 2016-04-11 22:17:37 | pgsql: Fix freshly-introduced PL/Python portability bug. |