To: Michael Monnerie <michael.monnerie@it-management.at>
cc: pgsql-admin@postgresql.org
Subject: Re: duplicate primary index in bayes db from SpamAssassin 
In-reply-to: <200804170945.51400@zmi.at> 
References: <200804141757.21574@zmi.at> <200804160156.43961@zmi.at>
	<200804170945.51400@zmi.at>
Comments: In-reply-to Michael Monnerie <michael.monnerie@it-management.at>
	message dated "Thu, 17 Apr 2008 09:45:50 +0200"
Date: Thu, 17 Apr 2008 11:41:31 -0400
Message-ID: <20473.1208446891@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

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