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
Attachment:
signature.asc
Description: This is a digitally signed message part.
