From: Michael Monnerie <michael.monnerie@it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: duplicate primary index in bayes db from SpamAssassin
Date: Wed, 7 May 2008 16:42:38 +0200
Message-ID: <200805071642.39041@zmi.at> (raw)
In-Reply-To: <6626.1210170774@sss.pgh.pa.us>
References: <200804141757.21574@zmi.at>
<200805071103.53981@zmi.at>
<6626.1210170774@sss.pgh.pa.us>
On Mittwoch, 7. Mai 2008 Tom Lane wrote:
> pg_dump intentionally does *not* look at the contents of indexes (at
> least not any on user tables). I think this is a good thing because
> it makes it more likely that you can dump a damaged database.
> pg_dump is not supposed to be some kind of fsck-like tool.
OK, I see that normally you should get that info out of the postgresql
log. The problem with this application is, that often it happens to try
an insert on already existing primary keys, which makes you overlook
the problem is real. Maybe something can be improved here, but I don't
know what would be the best way. Maybe a big log line like
YOUR DATABASE xxx SEEMS TO BE DAMAGED - PLEASE CHECK
such a line would jump into the eyes even on a big log, and it makes you
nervous enough to really check things.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: www.keyserver.net Key-ID: 1C1209B4
Attachments:
signature.asc (application/pgp-signature, 193B) download
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: michael.monnerie@it-management.at
Subject: Re: duplicate primary index in bayes db from SpamAssassin
In-Reply-To: <200805071642.39041@zmi.at>
* 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