Re: ERROR: Index pg_toast_8443892_index is not a btree

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: strk <strk(at)keybit(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: Index pg_toast_8443892_index is not a btree
Date: 2003-12-09 02:05:37
Message-ID: 25823.1070935537@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-12-09 03:28:04 Re: Something's not (de)compressing right
Previous Message Christopher Kings-Lynne 2003-12-09 01:50:50 Re: ERROR: Index pg_toast_8443892_index is not a btree