From: John Lister <john.lister-ps@kickstone.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: database corruption help
Date: Mon, 09 Feb 2009 20:09:22 +0000
Message-ID: <49908D72.7040904@kickstone.com> (raw)
In-Reply-To: <20151.1234208044@sss.pgh.pa.us>
References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com>
<17205.1234200693@sss.pgh.pa.us>
<AB15E89CD7FB4EBD9D76CC5F8D8B3D4E@squarepi.com>
<4990840C.4090900@kickstone.com>
<20151.1234208044@sss.pgh.pa.us>
>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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: john.lister-ps@kickstone.com, tgl@sss.pgh.pa.us
Subject: Re: database corruption help
In-Reply-To: <49908D72.7040904@kickstone.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox