| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 22:26:12 |
| Message-ID: | ec1e7a22-efc9-3472-7c05-664baba0935c@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 20/01/2021 17:25, Tom Lane wrote:
> 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"?
Any GiST index that's been concurrently inserted might be corrupt.
Better reindex all GiST indexes.
- Heikki
P.S. The GiST amcheck extension that's been discussed at [1] would catch
this corruption, so if that was already committed, we could suggest
using it. But that doesn't help us now.
[1]
https://www.postgresql.org/message-id/CAF3eApa07-BajjG8+RYx-Dr_cq28ZA0GsZmUQrGu5b2ayRhB5A@mail.gmail.com
would catch this corruption
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-20 23:19:16 | Re: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory |
| Previous Message | PG Bug reporting form | 2021-01-20 21:04:56 | BUG #16831: Idle postgres processes on Linux consumes huge amount of memory |