pgsql: Consistently use PG_INT(16|32|64)_(MIN|MAX).

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Consistently use PG_INT(16|32|64)_(MIN|MAX).
Date: 2017-12-13 02:21:06
Message-ID: E1eOwfS-0000Fq-TX@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Consistently use PG_INT(16|32|64)_(MIN|MAX).

Per buildfarm animal woodlouse.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f512a6e1323eefa843a063e466babb96d7bfb4ce

Modified Files
--------------
contrib/btree_gist/btree_cash.c | 2 +-
contrib/btree_gist/btree_int2.c | 2 +-
contrib/btree_gist/btree_int4.c | 2 +-
contrib/btree_gist/btree_int8.c | 2 +-
src/backend/utils/adt/int.c | 6 +++---
src/backend/utils/adt/int8.c | 10 +++++-----
src/backend/utils/adt/numeric.c | 2 +-
7 files changed, 13 insertions(+), 13 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-12-13 07:53:29 pgsql: Add float.h include to int8.c, for isnan().
Previous Message Peter Eisentraut 2017-12-13 02:03:17 pgsql: PL/Python: Fix potential NULL pointer dereference