Michael Banck <michael.banck@credativ.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
