Re: Reproducible GIST index corruption under concurrent updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Reproducible GIST index corruption under concurrent updates
Date: 2021-01-20 15:25:10
Message-ID: 594958.1611156310@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas <hlinnaka(at)iki(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-01-20 15:38:53 Re: Bug Report | Using ts_headline with the <-> operator
Previous Message christian 2021-01-20 12:37:46 Bug Report | Using ts_headline with the <-> operator