pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Duncan Sands <duncan.sands@deepbluecap.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Reproducible GIST index corruption under concurrent updates
Date: Wed, 20 Jan 2021 10:25:10 -0500
Message-ID: <594958.1611156310@sss.pgh.pa.us> (raw)
In-Reply-To: <b9cee27d-0ce9-7708-d197-580f62e5dab7@iki.fi>
References: <a9690483-6c6c-3c82-c8ba-dc1a40848f11@deepbluecap.com>
	<28663562-8489-4680-BC26-CAEADEB258D1@yandex-team.ru>
	<132baf64-3764-0351-750e-0443e74f1052@iki.fi>
	<907491b3-87c7-aadd-3fb1-be3c542b7fb7@iki.fi>
	<55ea6133-f2d1-0cc5-8ce5-333e373164ba@deepbluecap.com>
	<b9cee27d-0ce9-7708-d197-580f62e5dab7@iki.fi>

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





view thread (8+ messages)  latest in thread

Message-ID: <594958.1611156310@sss.pgh.pa.us>
Permalink:  ../594958.1611156310@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/594958.1611156310@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, hlinnaka@iki.fi, duncan.sands@deepbluecap.com, x4mmm@yandex-team.ru, pgsql-bugs@lists.postgresql.org
  Subject: Re: Reproducible GIST index corruption under concurrent updates
  In-Reply-To: <594958.1611156310@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox