| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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>, Michael Paquier <michael(at)paquier(dot)xyz>, Петър Славов <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-25 17:32:43 |
| Message-ID: | CAH2-Wz=cDCzrfwm8YYF4vd8oMNJtVRh+_BbCqhCrKzX1NgXzQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 25, 2022 at 10:18 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Right, I mean I'm not saying I *like* reverting, and I'm not disputing
> it's a good feature. Just that, if we have to choose between this
> feature and not having index corruption, we better not have index
> corruption.... and I'm not seeing any way that we can just tweak this
> and make it work.
Are we any closer to deciding on a timeline, in light of recent discussion?
I'm now convinced that an out-of-schedule release is probably the way
to go. My thinking is: are we really going to make users wait for
August 11th for a fix?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-05-25 19:16:17 | BUG #17498: Receive Failed: (error code 1) when importing any csv file from pgAdmin with no explanations |
| Previous Message | Robert Haas | 2022-05-25 17:17:49 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |