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: Thu, 12 Feb 2009 21:45:35 +0000
Message-ID: <4994987F.1030204@kickstone.com> (raw)
In-Reply-To: <17204.1234474784@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>
<49908D72.7040904@kickstone.com>
<25753.1234224090@sss.pgh.pa.us>
<4991338B.704@kickstone.com>
<4994906B.6090408@kickstone.com>
<17204.1234474784@sss.pgh.pa.us>
I'm running ubuntu and can see references to only one log file which i'm
assuming is the postmaster log..
Anyway the only relevant bits are:
GMT LOG: relation "pg_class" TID 15538/4: dead HOT-updated tuple ---
cannot shrink relation
2009-02-12 21:06:40 GMT STATEMENT: VACUUM FULL VERBOSE ANALYZE pg_class
2009-02-12 21:06:40 GMT WARNING: index "pg_class_relname_nsp_index"
contains 1818 row versions, but table contains 1813 row versions
If that helps...
Thanks
> John Lister <john.lister-ps@kickstone.com> writes:
>
>> I seem to have more dead rows now..
>> doing a vacuum full on pg_class gives me
>>
>
>
>> INFO: vacuuming "pg_catalog.pg_class"INFO: "pg_class": found 37
>> removable, 1845 nonremovable row versions in 18905 pages
>> DETAIL: 27 dead row versions cannot be removed yet.
>> Nonremovable row versions range from 160 to 229 bytes long.
>> There were 933834 unused item pointers.
>> Total free space (including removable row versions) is 150368692 bytes.
>> 18839 pages are or will become empty, including 0 at the end of the table.
>> 0 pages containing 0 free bytes are potential move destinations.
>>
>
> Hmm, that last seems to indicate that do_shrinking has been reset.
> It looks like the cases where that happens are reported with elog(LOG)
> which means they probably only went to the postmaster log (maybe we
> should fix things so that vacuum verbose reports those). What have
> you got in the postmaster log?
>
> regards, tom lane
>
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: <4994987F.1030204@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