From: Florian Weimer <fweimer@bfk.de>
To: pgsql-hackers@postgresql.org
Subject: Re: Hmmm ... isn't count_nondeletable_pages all wet?
Date: Mon, 29 Oct 2007 13:48:08 +0100
Message-ID: <82wst6ulx3.fsf@mid.bfk.de> (raw)
In-Reply-To: <29644.1189904237@sss.pgh.pa.us>
References: <28916.1189900143@sss.pgh.pa.us>
<29644.1189904237@sss.pgh.pa.us>
* Tom Lane:
> I am fairly sure that this bug explains problems previously reported
> by Merlin Moncure:
> http://archives.postgresql.org/pgsql-general/2006-10/msg01312.php
> and Florian Weimer:
> http://archives.postgresql.org/pgsql-general/2006-11/msg00305.php
> In both those cases, off-list investigation showed that the symptoms
> were caused by multiple index entries pointing to the same heap tuples,
> where one index entry matched the actual contents of the row and
> the other did not. In both cases this occurred for a fairly small
> number of rows that were clumped together into small ranges of blocks.
> It looks to me like this is perfectly explained by the theory that
> that range of blocks had been truncated away by a VACUUM at some point
> in the table's history, and that the non-matching index entries stemmed
> from an insert or update that occurred and then aborted after VACUUM had
> examined the blocks the first time but before it could return to check
> whether the blocks were still empty.
We did have auto-vacuum running, and while the table in question was
supposedly INSERT-only, some rollback might have occurred before the
corruption hit us, resulting in the dead tuples. So your explanation
makes sense to me (but I'm not really familiar with PostgreSQL
internals).
Regarding Scott's commment of other reports, I don't think we've
experienced the issue again; we've switched servers since then, and
the usage patterns have changed over time.
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
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: fweimer@bfk.de, pgsql-hackers@postgresql.org
Subject: Re: Hmmm ... isn't count_nondeletable_pages all wet?
In-Reply-To: <82wst6ulx3.fsf@mid.bfk.de>
* 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