| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Петър Славов <pet(dot)slavov(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |
| Date: | 2022-05-26 03:39:20 |
| Message-ID: | Yo72aOILTPjBldWU@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 25, 2022 at 11:17:33PM -0400, Bruce Momjian wrote:
> * Caused by CREATE/REINDEX CONCURRENTLY
Yes.
> * No way to detect which indexes were created concurrently
> * amcheck will be required to find corrupt indexes (options?)
amcheck would help for btree, not the other AMs. I am not sure but
there could be other symptoms that may not be detected by amcheck?
> * Heap is fine, only index is corrupt
Yes.
> * Bug since PG 14
14.0, yes.
> * Not known why reports are only appearing now
> * Feature will likely need to be removed rather than fixed
Trends go in this direction. It does not seem like there is a
complete conclusion on this point, either.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-05-26 03:46:49 | Re: BUG #17495: Regression in 15beta1 when filtering subquery including row_number window function |
| Previous Message | Bruce Momjian | 2022-05-26 03:17:33 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |