[COMMITTERS] pgsql: Avoid -Wconversion warnings from direct use of GET_n_BYTESmacro - Mailing list pgsql-committers

From Tom Lane
Subject [COMMITTERS] pgsql: Avoid -Wconversion warnings from direct use of GET_n_BYTESmacro
Date
Msg-id E1dG5Wy-0001m2-KB@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Avoid -Wconversion warnings from direct use of GET_n_BYTES macros.

The GET/SET_n_BYTES macros are meant to be infrastructure for the
DatumGetFoo/FooGetDatum macros, which include a cast to the intended
target type.  Using them directly without a cast, as DatumGetFloat4
and friends previously did, can yield warnings when -Wconversion is on.
This is of little significance when building Postgres proper, because
there are such a huge number of such warnings in the server that nobody
would think -Wconversion is of any use.  But some extensions build with
-Wconversion due to outside constraints.  Commit 14cca1bf8 did a disservice
to those extensions by moving DatumGetFloat4 et al into postgres.h,
where they can now cause warnings in extension builds.

To fix, use DatumGetInt32 and friends in place of the low-level macros.
This is arguably a bit cleaner anyway.

Chapman Flack

Discussion: https://postgr.es/m/592E4D04.1070609@anastigmatix.net

Branch
------
master

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

Modified Files
--------------
src/include/postgres.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Sort syscache identifiers into alphabetical order.
Next
From: Peter Eisentraut
Date:
Subject: [COMMITTERS] pgsql: doc: Add another migration item to release notes