Re: ERROR: Index pg_toast_8443892_index is not a btree - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ERROR: Index pg_toast_8443892_index is not a btree
Date
Msg-id 25823.1070935537@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: Index pg_toast_8443892_index is not a btree  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: ERROR: Index pg_toast_8443892_index is not a btree  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> Is there anything stopping us going through the code and finding all 
> ereports that can be fixed by a REINDEX, and issue a HINT with all of 
> them saying that they should REINDEX the broken index?

How would you know which ones correspond to REINDEX-fixable conditions?

I generally dislike hints that tell people their first action should be
to destroy the evidence, anyway.  If they had an index problem, REINDEX
will guarantee there is no chance of learning anything about it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: ERROR: Index pg_toast_8443892_index is not a btree
Next
From: Tom Lane
Date:
Subject: Re: Something's not (de)compressing right