Re: Backpatching nbtree VACUUM (page deletion) hardening
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-09-05T18:22:36Z
Lists: 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
Commits
-
Backpatch nbtree page deletion hardening.
- 43e409cea468 13.9 landed
- 7adc34832f24 12.13 landed
- a228cca46d7d 11.18 landed
- cfe41f9766a1 10.23 landed
-
nbtree VACUUM: Cope with buggy opclasses.
- 5b861baa550a 14.0 cited