| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Alexey Ermakov <alexey(dot)ermakov(at)dataegret(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently |
| Date: | 2021-11-07 00:06:55 |
| Message-ID: | E6013BD3-5114-4338-AA03-7FBBE23FEC33@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On November 4, 2021 1:01:44 PM PDT, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)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(at)*** 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Semab Tariq | 2021-11-07 15:25:09 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
| Previous Message | Noah Misch | 2021-11-06 23:08:46 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |