Re: Backpatching nbtree VACUUM (page deletion) hardening

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: Backpatching nbtree VACUUM (page deletion) hardening
Date: 2022-09-05 18:22:36
Message-ID: CAH2-Wzm9OBaQPmSZqxAy_PmUzDHa1xywqcQL4E=2LAeWXDL5EA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 2, 2022 at 6:51 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Yes -- nbtree VACUUM generally can cope quite well, even when the
> index is corrupt. It should mostly manage to do what is expected here,
> even with a misbehaving opclass, because it relies as little as
> possible on user-defined opclass code.

I just backpatched the hardening commit from 14 to every supported branch.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-09-05 18:56:30 Re: predefined role(s) for VACUUM and ANALYZE
Previous Message Ranier Vilela 2022-09-05 18:07:27 Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)