From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Reduce scope of heap vacuum per_buffer_data |
Date: | 2025-02-18 16:24:31 |
Message-ID: | CAAKRu_aGVuq3VUV4SoCOtAubMipY7u=X6sBXsUS+tRQ_+bAVuA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Tue, Feb 18, 2025 at 9:30 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> 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.
Realized I forgot an important word in the commit message.
per_buffer_data doesn't point to the block number. It points to info
about the next block. Commit message should say "the read stream API
returns a pointer to information about the next block to vacuum". Oh
well... There is nothing I can do now.
- Melanie
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2025-02-18 18:38:00 | pgsql: Update outdated comments in nodeAgg.c. |
Previous Message | Melanie Plageman | 2025-02-18 14:30:04 | pgsql: Reduce scope of heap vacuum per_buffer_data |