Re: Allow cancelling VACUUM of nbtrees with corrupted right links
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2018-06-27T19:49:56Z
Lists: pgsql-hackers
On Wed, Jun 27, 2018 at 12:18 PM, Andres Freund <andres@anarazel.de> wrote: > It's possibly wrong that it's unreachable - I've just not managed to get > there. If somebody has an idea how to build a reproducible case to reach > it... Set a breakpoint in _bt_unlink_halfdead_page() after the initial "LockBuffer(leafbuf, BUFFER_LOCK_UNLOCK);", and then provoke a page split in the left sibling by carefully inserting values that belong within its part of the key space? I would probably attempt this with an index on text, so that I could contrive as many key values that belong on the left sibling as needed. You're probably looking at a test-case that doesn't involve a multi-level deletion, where the leaf and target page are the same. Not sure if you want to reproduce the multi-level deletion case independently. -- Peter Geoghegan
Commits
-
Check for interrupts inside the nbtree page deletion code.
- 0c69db762d88 11.0 landed
- 0095809890dd 10.5 landed
- f411108c9fe9 9.5.14 landed
- 8c8c9f37c283 9.4.19 landed
- 2adadf018bd4 9.6.10 landed
- 3a01f68e35a3 12.0 landed