From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul B. Anderson <paul.a@pnlassociates.com>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Vacuum error on database postgres
Date: Fri, 01 Sep 2006 10:41:09 -0400
Message-ID: <4001.1157121669@sss.pgh.pa.us> (raw)
In-Reply-To: <44F82150.5000809@pnlassociates.com>
References: <44F82150.5000809@pnlassociates.com>
"Paul B. Anderson" <paul.a@pnlassociates.com> writes:
> I did delete exactly one of each of these using ctid and the query then
> shows no duplicates. But, the problem comes right back in the next
> database-wide vacuum.
That's pretty odd --- I'm inclined to suspect index corruption.
> I also tried reindexing the table.
Get rid of the duplicates (actually, I'd just blow away all the
pg_statistic entries for each of these tables) and *then* reindex.
Then re-analyze and see what happens.
Worst case you could just delete everything in pg_statistic, reindex it,
do a database-wide ANALYZE to repopulate it. By definition there's not
any original data in that table...
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, paul.a@pnlassociates.com
Subject: Re: Vacuum error on database postgres
In-Reply-To: <4001.1157121669@sss.pgh.pa.us>
References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us>
* 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