pgsql: Reduce scope of heap vacuum per_buffer_data

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Reduce scope of heap vacuum per_buffer_data
Date: 2025-02-18 14:30:04
Message-ID: E1tkObs-007o8B-E1@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Reduce scope of heap vacuum per_buffer_data

Move lazy_scan_heap()'s per_buffer_data variable into a tighter scope.
In lazy_scan_heap()'s phase I heap vacuuming, the read stream API
returns a pointer to the next block number to vacuum. As long as
read_stream_next_buffer() returns a valid buffer, per_buffer_data should
always be valid.

Move per_buffer_data into a tighter scope and make sure it is reset to
NULL on each iteration so that we get a core dump instead of bogus data
from a previous block if something goes wrong in the read stream API.

Suggested-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/626104.1739729538%40sss.pgh.pa.us

Branch
------
master

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

Modified Files
--------------
src/backend/access/heap/vacuumlazy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Melanie Plageman 2025-02-18 16:24:31 Re: pgsql: Reduce scope of heap vacuum per_buffer_data
Previous Message Daniel Gustafsson 2025-02-18 12:24:15 pgsql: Add PGErrorVerbosity to typedefs.list