Re: Backpatching nbtree VACUUM (page deletion) hardening - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Backpatching nbtree VACUUM (page deletion) hardening
Date
Msg-id CAH2-Wzm9OBaQPmSZqxAy_PmUzDHa1xywqcQL4E=2LAeWXDL5EA@mail.gmail.com
Whole thread Raw
In response to Re: Backpatching nbtree VACUUM (page deletion) hardening  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Fri, Sep 2, 2022 at 6:51 PM Peter Geoghegan <pg@bowt.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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)
Next
From: Nathan Bossart
Date:
Subject: Re: predefined role(s) for VACUUM and ANALYZE