lazy_scan_heap: avoid vacuum block, already vacuumed (src/backend/access/heap/vacuumlazy.c)

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: lazy_scan_heap: avoid vacuum block, already vacuumed (src/backend/access/heap/vacuumlazy.c)
Date: 2026-07-03 12:02:28
Message-ID: CAEudQAokA6dgw9eOF=bLC-FNEtk52oasVfVMgU0TUFcTtT=7hQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.

lazy_scan_heap: avoid vacuum block, already vacuumed.

Previously, in lazy_scan_heap() *next_fsm_block_to_vacuum*
is set with blkno, but FreeSpaceMapVacuumRange uses an exclusive end,
so passing blkno + 1 covers blkno itself.

Advance *next_fsm_block_to_vacuum* to blkno + 1, so the next call begins
at the first unvacuumed block and does not re-vacuum blkno.

best regards,
Ranier Vilela

Attachment Content-Type Size
avoid-revaccum-block-vacuumlazy.patch application/octet-stream 969 bytes

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-07-03 12:10:30 Re: Fix tracing of BackendKeyData and CancelRequest messages
Previous Message Nisha Moond 2026-07-03 11:55:07 Re: Proposal: Conflict log history table for Logical Replication