| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, 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 05:43:08 |
| Message-ID: | YfTT7BBonfQYLPdX@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jan 28, 2022 at 07:00:31PM -0800, Peter Geoghegan wrote:
> If I had to guess, then I'd guess that this has something to do with
> orphaned HOT chains, like those we saw in the bug report that led to
> bugfix commit 18b87b20 (which is in 14.2 but not 14.1). I could easily
> be wrong about that, so take it with a grain of salt. I find it a
> little suspicious that we're hearing about a REINDEX CONCURRENTLY
> problem in Postgres 14, which is much less mature than Postgres 12
> (where REINDEX CONCURRENTLY first appeared).
Possible, but hard to say without an actual proof. Maxim, if the
problem is reproducible easily on your end, could you give a try to v12
and v13 and see if it happens as well there?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2022-01-29 15:23:49 | Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table |
| Previous Message | Tom Lane | 2022-01-29 03:44:04 | Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) |