Re: database corruption help

>Yeah, if you have reason not to trust the system indexes then -P is
>a good idea until they are fixed. Standalone mode per se isn't that
>important --- you could do this from a regular session with -P specified
>via PGOPTIONS.

still getting the same problem.

> PGOPTIONS="-P"
> psql backend
>> reindex system backend;
>> NOTICE: table "pg_class" was reindexed
>> NOTICE: table "pg_statistic" was reindexed
>> NOTICE: table "pg_ts_config" was reindexed ...

>> vacuum full verbose pg_class

>> INFO: vacuuming "pg_catalog.pg_class"
>> INFO: "pg_class": found 7 removable, 1839 nonremovable row versions
in 18812 pages
>> DETAIL: 27 dead row versions cannot be removed yet.
>> Nonremovable row versions range from 160 to 229 bytes long.
>> There were 929452 unused item pointers.
>> Total free space (including removable row versions) is 149628172 bytes.
>> 18749 pages are or will become empty, including 0 at the end of the
table.
>> 0 pages containing 0 free bytes are potential move destinations.
>> CPU 0.01s/0.07u sec elapsed 0.17 sec.
>> INFO: index "pg_class_oid_index" now contains 1812 row versions in
7 pages
>> DETAIL: 0 index row versions were removed.
>> 0 index pages have been deleted, 0 are currently reusable.
>> CPU 0.00s/0.01u sec elapsed 0.09 sec.
>> WARNING: index "pg_class_oid_index" contains 1812 row versions, but
table contains 1807 row versions
>> HINT: Rebuild the index with REINDEX.
>> INFO: index "pg_class_relname_nsp_index" now contains 1812 row
versions in 23 pages
>> DETAIL: 0 index row versions were removed.
>> 0 index pages have been deleted, 0 are currently reusable.
>> CPU 0.00s/0.01u sec elapsed 0.09 sec.
>> WARNING: index "pg_class_relname_nsp_index" contains 1812 row
versions, but table contains 1807 row versions
>> HINT: Rebuild the index with REINDEX.

Just noticed the 7 dead rows above, are they likely to be causing a
problem?
BTW this is postgresql 8.3.5 if that makes a difference...

I'm guessing it is fairly important to get rid of these warnings....

Thanks