Horton

Re: BUG #17268: Possible corruption in toast index after reindex index concurrently

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: pgsql-bugs@lists.postgresql.org, Maxim Boguk <maxim.boguk@gmail.com>, Peter Geoghegan <pg@bowt.ie>
Cc: Alexey Ermakov <alexey.ermakov@dataegret.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Michael Paquier <michael@paquier.xyz>
Date: 2021-11-07T00:06:55Z
Lists: pgsql-bugs 
Hi, 

On November 4, 2021 1:01:44 PM PDT, Maxim Boguk <maxim.boguk@gmail.com> wrote:
>UPDATE: the problem base table entry which had erroneous toast data
>definitely had been created during the REINDEX run of toast idx.

Do you have any details about the transaction / application that inserted the data?


>2021-11-02 13:15:45.469 UTC 2379 postgres@*** from [local] [vxid:24/0
>txid:0] [REINDEX] LOG:  duration: 1719120.441 ms  statement: REINDEX
>INDEX CONCURRENTLY pg_toast.pg_toast_2624976286_index
>and the problem entry had been created at 2021-11-02 13:04:22.192125 UTC.
>
>So there seems some subtle bug with indexing new toast data during
>REINDEX INDEX CONCURRENTLY of the toast index.

Any chance you're using prepared transactions?

Regards,

Andres
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Commits

  1. Fix corruption of toast indexes with REINDEX CONCURRENTLY