diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2025-01-08 07:50:30 +1300 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2025-01-08 10:43:40 +1300 |
| commit | 66aaabe7a18f2bc5d22cd832ad612ba5bab18d7b (patch) | |
| tree | b3b47210642074a90e826df848f56136c357a65a /src/backend/utils/adt/ruleutils.c | |
| parent | e43537cdc36146f1becc0084b1acc24a46074ae6 (diff) | |
| download | postgresql-66aaabe7a18f2bc5d22cd832ad612ba5bab18d7b.tar.gz postgresql-66aaabe7a18f2bc5d22cd832ad612ba5bab18d7b.zip | |
Restore smgrtruncate() prototype in back-branches.
It's possible that external code is calling smgrtruncate(). Any
external callers might like to consider the recent changes to
RelationTruncate(), but commit 38c579b0 should not have changed the
function prototype in the back-branches, per ABI stability policy.
Restore smgrtruncate()'s traditional argument list in the back-branches,
but make it a wrapper for a new function smgrtruncate2(). The three
callers in core can use smgrtruncate2() directly. In master (18-to-be),
smgrtruncate2() is effectively renamed to smgrtruncate(), so this wart
is cleaned up.
Reviewed-by: Michael Paquier <michael@paquier.xyz>
Discussion: https://postgr.es/m/CA%2BhUKG%2BThae6x6%2BjmQiuALQBT2Ae1ChjMh1%3DkMvJ8y_SBJZrvA%40mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/ruleutils.c')
0 files changed, 0 insertions, 0 deletions