Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT - Mailing list pgsql-general

From Tom Lane
Subject Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT
Date
Msg-id 20203.1084232982@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
Andrew Sullivan <ajs@crankycanuck.ca> writes:
> Dunno if this is any help, but on a 7.2 system I saw a REINDEX which
> was interrupted leave the index at least partially working.  We ended
> up with an index which seemed fine, but which didn't contain certain
> rows (so those rows were not visible when the SELECT criterion was
> the indexed field).  This was extremely puzzling, but a DROP INDEX;
> CREATE INDEX pair solved it.

Hmm, I would expect that behavior for an overwrite-in-place REINDEX,
but 7.2 only seems to use overwrite-in-place for critical system
catalogs.  What were you reindexing exactly?  Were you running a
standalone backend?

            regards, tom lane

pgsql-general by date:

Previous
From: Steve Atkins
Date:
Subject: Re: nested elseif woes
Next
From: pw
Date:
Subject: query of database to get permitted users list