Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E75E0632D80 for ; Mon, 9 Feb 2009 16:18:54 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88012-10 for ; Mon, 9 Feb 2009 16:18:50 -0400 (AST) X-Greylist: delayed 00:09:40.076462 by SQLgrey-1.7.6 Received: from mk-filter-4-a-1.mail.uk.tiscali.com (mk-filter-4-a-1.mail.uk.tiscali.com [212.74.100.55]) by mail.postgresql.org (Postfix) with ESMTP id 9E1DC62FBA6 for ; Mon, 9 Feb 2009 16:18:50 -0400 (AST) X-Trace: 142339716/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/80.225.1.137/None/john.lister-ps@kickstone.com X-SBRS: None X-RemoteIP: 80.225.1.137 X-IP-MAIL-FROM: john.lister-ps@kickstone.com X-MUA: Thunderbird 2.0.0.19 (Windows/20081209) X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AloBADUckElQ4QGJ/2dsb2JhbAAI0UOEGgY X-IronPort-AV: E=Sophos;i="4.37,406,1231113600"; d="scan'208";a="142339716" Received: from 80-225-1-137.dynamic.dial.as9105.com (HELO [192.168.6.11]) ([80.225.1.137]) by smtp.tiscali.co.uk with ESMTP; 09 Feb 2009 20:09:08 +0000 Message-ID: <49908D72.7040904@kickstone.com> Date: Mon, 09 Feb 2009 20:09:22 +0000 From: John Lister User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: database corruption help References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com> <17205.1234200693@sss.pgh.pa.us> <4990840C.4090900@kickstone.com> <20151.1234208044@sss.pgh.pa.us> In-Reply-To: <20151.1234208044@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/64 X-Sequence-Number: 31285 >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