pgsql: Fix portability issues in 86c43f4e22c0771fd0cc6bce2799802c894ee2 - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix portability issues in 86c43f4e22c0771fd0cc6bce2799802c894ee2
Date
Msg-id E1aklfD-0001y8-Dx@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix portability issues in 86c43f4e22c0771fd0cc6bce2799802c894ee2ec.

INT64_MIN/MAX should be spelled PG_INT64_MIN/MAX, per well established
convention in our sources.  Less obviously, a symbol named DOUBLE causes
problems on Windows builds, so rename that to DOUBLE_CONST; and rename
INTEGER to INTEGER_CONST for consistency.

Also, get rid of incorrect/obsolete hand-munging of yycolumn, and fix
the grammar for float constants to handle expected cases such as ".1".

First two items by Michael Paquier, second two by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/656ee8489053aafc85324b9ef7e91b645674ffb9

Modified Files
--------------
src/bin/pgbench/exprparse.y | 10 +++++-----
src/bin/pgbench/exprscan.l  |  9 ++++++---
src/bin/pgbench/pgbench.c   |  2 +-
3 files changed, 12 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Don't require a user mapping for FDWs to work.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix zic for Windows.