Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: kehan5800(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
Date: 2026-10-23 02:01:29
Message-ID: CAHGQGwG6nGe+py-+VRnoDfDBkOQjm6yNOqeyhQ6x1C681vhFww@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 22, 2026 at 3:27 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> One possible fix is to have the summarizer mark the last remaining VM page
> as
> modified when it summarizes the truncation.

Thanks for the report and investigation! I've attached a patch based on
your approach, along with a TAP test that checks for stale VM bits after
restoring an incremental backup.

Regards,

--
Fujii Masao

Attachment Content-Type Size
v1-0001-Fix-stale-visibility-maps-in-incremental-backups-.patch application/octet-stream 6.8 KB
nocfbot-v1-0001-PG17-Fix-stale-visibility-maps-in-incremental-backups-.patch application/octet-stream 7.0 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-10-23 02:32:47 Re: BUG #19784: "no relation entry for relid 1" when costing = ANY (<array expr over max(col)>) in a MinMaxAggPath
Previous Message shihao zhong 2026-10-23 01:45:00 Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction