Dear list, I don't know whether pgsql-admin or the SA list is the
correct one to ask, so I start here. I have a bayes Postgres database
for SpamAssassin, which I use shared from 2 servers to have the same
content. I think this could be a locking issue or whatever, I don't
care. BUT: I have lots of "duplicate index" elements now, preventing a
restore or cleanup. Here's the dump and diff if anyone cares:
http://zmi.at/x/bayes_dup_idx.dump.bz2 (upload currently running)
Could the problem be caused by any settings to the DB, or because of the
stored procedures? Normally there should be no way this can happen, so
what can cause this?
// 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
pgsql-admin by date
|Next:||From: Tom Lane||Date: 2008-04-14 16:00:01|
|Subject: Re: duplicate primary index in bayes db from SpamAssassin |
|Previous:||From: Tom Lane||Date: 2008-04-14 15:45:37|
|Subject: Re: postgres 8.2.6 core dump when initialising. |