| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, 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-08 18:08:33 |
| Message-ID: | 20211108180833.5sph7vrnrv5zjrj3@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2021-11-04 22:01:44 +0200, Maxim Boguk wrote:
> 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.
Another question on this. Are you running multiple reindexes concurrently? Other
maintenance commands?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-11-08 18:32:39 | Re: BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum |
| Previous Message | Andres Freund | 2021-11-08 17:51:13 | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently |