Re: duplicate primary index in bayes db from SpamAssassin

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Monnerie <michael(dot)monnerie(at)it-management(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: duplicate primary index in bayes db from SpamAssassin
Date: 2008-05-07 14:32:54
Message-ID: 6626.1210170774@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Michael Monnerie <michael(dot)monnerie(at)it-management(dot)at> writes:
> So probably this is this kind of "should never ever happen" except your
> machine goes bye-bye badly. What makes me a bit worried is that pg_dump
> did not report an error at all, but made it's backup as if everything
> is OK. Could that be changed maybe so that in case of a problem it at
> least cries out loudly "broken db found" or so?

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.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Monnerie 2008-05-07 14:42:38 Re: duplicate primary index in bayes db from SpamAssassin
Previous Message Richard Broersma 2008-05-07 13:23:04 Re: column: on update update?