Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Consistently use PG_INT(16|32|64)_(MIN|MAX). - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: Consistently use PG_INT(16|32|64)_(MIN|MAX).
Date
Msg-id E1eOwfS-0000Fq-TX@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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(-)

pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: PL/Python: Fix potential NULL pointer dereference
Next
From: Andres Freund
Date:
Subject: pgsql: Add float.h include to int8.c, for isnan().