Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID
Date: 2024-12-23 20:47:35
Message-ID: CAH2-Wz=AH2eHAAYMgsDS+mT+kg23kV+ToYGXVVLYWwpv3pB2MA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 20, 2024 at 1:32 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Perhaps this patch should also explain why this is better this way?

See the commit message, and my remarks to Andrey just now.

> This path does not manipulate btpo_level, for one.

Why would it do so? Changing the btree level would corrupt the index?

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-12-23 21:17:44 Re: Document NULL
Previous Message Peter Geoghegan 2024-12-23 20:46:49 Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID