From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Monnerie <michael.monnerie@it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: duplicate primary index in bayes db from SpamAssassin
Date: Thu, 17 Apr 2008 11:41:31 -0400
Message-ID: <20473.1208446891@sss.pgh.pa.us> (raw)
In-Reply-To: <200804170945.51400@zmi.at>
References: <200804141757.21574@zmi.at>
<200804160156.43961@zmi.at>
<200804170945.51400@zmi.at>
Michael Monnerie <michael.monnerie@it-management.at> writes:
> I'd like to drop that broken db, or should I keep it for analyzation?
Looking back over the thread, it seems that the problems you saw could
be explained by the VACUUM-related bugs we fixed in 8.1.9 and 8.1.10;
although obviously this theory requires assuming that the dups were
there before you updated to 8.1.11. You didn't say much about time
frame so I don't know if that's plausible.
This latest bit with many fewer index entries than table entries is just
weird, though. The 8.1.10 VACUUM bug could have led to having *more*
index entries than table entries, but not the other way around.
Before you zap the database, would you be willing to make the actual
database files (not a dump, but the stored files) available? I'd
be interested to take a closer look at that index.
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: tgl@sss.pgh.pa.us, michael.monnerie@it-management.at
Subject: Re: duplicate primary index in bayes db from SpamAssassin
In-Reply-To: <20473.1208446891@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