pgsql: Make blkreftable API use size_t/ssize_t consistently - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Make blkreftable API use size_t/ssize_t consistently
Date
Msg-id E1wjJ5Q-0001AV-2U@gemulon.postgresql.org
Whole thread
List pgsql-committers
Make blkreftable API use size_t/ssize_t consistently

It was using int for the input and output length, where size_t or
ssize_t would be more appropriate.  It might not matter in practice,
but it makes the APIs consistent at all levels.

Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406@eisentraut.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/7b87f08e8778c2d38c95e3808419e2d18c55c672

Modified Files
--------------
src/backend/backup/walsummary.c       | 14 +++++++-------
src/bin/pg_walsummary/pg_walsummary.c | 10 +++++-----
src/common/blkreftable.c              | 16 ++++++++--------
src/include/backup/walsummary.h       |  4 ++--
src/include/common/blkreftable.h      |  2 +-
5 files changed, 23 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Translation updates
Next
From: Tom Lane
Date:
Subject: pgsql: Stamp 19beta2.