Re: Reproducible GIST index corruption under concurrent updates

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Heikki Linnakangas <hlinnaka@iki.fi>

Cc: Duncan Sands <duncan.sands@deepbluecap.com>, Andrey Borodin <x4mmm@yandex-team.ru>, pgsql-bugs@lists.postgresql.org

Date: 2021-01-20T15:25:10Z

Lists: pgsql-bugs

Heikki Linnakangas <hlinnaka@iki.fi> writes:
> Pushed as commit 6b4d3046f4, and backpatched down to version 12, where 
> this bug was introduced. It will appear in the next minor release.

I see you noted that REINDEX is required to repair any corrupted indexes.
For the purposes of the release notes, can we characterize which indexes
might be affected, or do we just have to say "better reindex all GIST
indexes"?

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix bug in detecting concurrent page splits in GiST insert
- 0326635dd484 12.6 landed
- b8403d140f4e 13.2 landed
- 6b4d3046f422 14.0 landed
Refactor checks for deleted GiST pages.
- e2e992c93145 12.0 cited