Horton

Re: Avoiding another needless ERROR during nbtree page deletion

Peter Geoghegan <pg@bowt.ie>

View thread View on postgr.es
From: Peter Geoghegan <pg@bowt.ie>
To: Greg Stark <stark@mit.edu>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-01T12:14:28Z
Lists: pgsql-hackers 
On Thu, Jun 1, 2023 at 6:47 AM Greg Stark <stark@mit.edu> wrote:
> What error would one expect to see? I did have a case where vacuum was erroring on a btree in $previous_job.

You mean in general? It's usually this one:

https://gitlab.com/gitlab-org/gitlab/-/issues/381443

In the case of this particular issue, the error is "right sibling's
left-link doesn't match". Per:

https://stackoverflow.com/questions/49307292/error-in-postgresql-right-siblings-left-link-doesnt-match-block-5-links-to-8

-- 
Peter Geoghegan

Commits

  1. nbtree VACUUM: cope with right sibling link corruption.

  2. Backpatch nbtree page deletion hardening.

  3. nbtree VACUUM: Cope with buggy opclasses.