| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Banck <michael(dot)banck(at)credativ(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Release notes for February minor releases |
| Date: | 2022-02-04 21:35:07 |
| Message-ID: | 434393.1644010507@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Banck <michael(dot)banck(at)credativ(dot)de> writes:
> On Fri, Feb 04, 2022 at 02:58:59PM -0500, Tom Lane wrote:
>> + If this seems to have affected a table, <command>REINDEX</command>
>> + should repair the damage.
> I don't think this is very helpful to the reader, are their indexes
> corrupt or not? If we can't tell them a specific command to run to
> check, can we at least mention that running amcheck would detect that
> (if it actually does)? Otherwise, I guess the only way to be sure is to
> just reindex every index? Or is this at least specific to b-trees?
Yeah, I wasn't too happy with that advice either, but it seems like the
best we can do [1]. I don't think we should advise blindly reindexing
your whole installation, because it's a very low-probability bug.
regards, tom lane
[1] https://www.postgresql.org/message-id/20220204041935.gf4uwbdxddq6rffh%40alap3.anarazel.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-02-04 21:41:03 | Re: Release notes for February minor releases |
| Previous Message | Tom Lane | 2022-02-04 21:29:19 | Re: Release notes for February minor releases |