| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table |
| Date: | 2022-01-29 02:34:18 |
| Message-ID: | 20220129023418.GA2452893@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jan 28, 2022 at 04:17:28PM +0200, Maxim Boguk wrote:
> On Fri, Jan 28, 2022 at 3:42 PM PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> > PostgreSQL version: 14.1
> Seems something broken in combination of HOT update and REINDEX
> CONCURRENTLY.
Agreed. Can you create a self-contained test case, perhaps by adapting
contrib/amcheck/t/002_cic.pl? If this bug is like the ones fixed between 14.0
and 14.1, the base backup and WAL won't help us, unfortunately. The transient
states are what matter. I did try modifying the test to have elements of your
scenario, including HOT updates, KEY SHARE locks, and frozen tuples. That
didn't reproduce the bug. I'm attaching what I tried.
| Attachment | Content-Type | Size |
|---|---|---|
| repro-reindex-hot-v0.patch | text/plain | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-01-29 03:00:31 | Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table |
| Previous Message | Tom Lane | 2022-01-28 23:48:00 | Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) |