| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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 14:41:28 |
| Message-ID: | BB3FB2D1-9796-442B-AF11-08DFD0BF0F57@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On May 26, 2022, at 07:40, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> Uh, if people don't know if they have used CREATE/REINDEX CONCURRENTLY
> in PG 14.0+, they are going to need to run amcheck on all btree indexes
> and reindex all non-btree indexes? That is going to be a painful
> message to deliver, and hear. :-(
Unless we are 100% sure that amcheck will never return a false negative in this situation, we may have to recommend reindexing everything. Ouch.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-05-26 14:48:27 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |
| Previous Message | Bruce Momjian | 2022-05-26 14:40:03 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |