pgsql: Make blkreftable API use size_t/ssize_t consistently

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make blkreftable API use size_t/ssize_t consistently
Date: 2026-07-13 16:00:53
Message-ID: E1wjJ5Q-0001AV-2U@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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(at)iki(dot)fi>
Discussion: https://www.postgresql.org/message-id/flat/f9aab072-0078-49e4-ab93-3b08086a4406(at)eisentraut(dot)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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2026-07-13 20:04:07 pgsql: Stamp 19beta2.
Previous Message Melanie Plageman 2026-07-13 13:31:46 Re: pgsql: Update FSM after updating VM on-access