pgsql: Introduce 'options' argument to heap_page_prune()

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Introduce 'options' argument to heap_page_prune()
Date: 2024-04-01 21:56:56
Message-ID: E1rrPeB-0002LN-V1@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Introduce 'options' argument to heap_page_prune()

Currently there is only one option, HEAP_PAGE_PRUNE_MARK_UNUSED_NOW
which replaces the old boolean argument, but upcoming patches will
introduce at least one more. Having a lot of boolean arguments makes
it hard to see at the call sites what the arguments mean, so prefer a
bitmask of options with human-readable names.

Author: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Author: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Discussion: https://www.postgresql.org/message-id/20240401172219.fngjosaqdgqqvg4e@liskov

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3d0f730bf19fbc70cca58818c1ad7415e5aa7d62

Modified Files
--------------
src/backend/access/heap/pruneheap.c | 11 ++++++-----
src/backend/access/heap/vacuumlazy.c | 9 ++++++---
src/include/access/heapam.h | 5 ++++-
3 files changed, 16 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2024-04-01 23:01:45 pgsql: Avoid "unused variable" warning on non-USE_SSL_ENGINE platforms.
Previous Message Tom Lane 2024-04-01 20:46:40 pgsql: Rearrange pg_dump's handling of large objects for better efficie