Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 3C1192E0031 for ; Mon, 14 Apr 2008 12:57:32 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 07845-10 for ; Mon, 14 Apr 2008 12:57:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by developer.postgresql.org (Postfix) with ESMTP id 6DF892E0051 for ; Mon, 14 Apr 2008 12:57:25 -0300 (ADT) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id E43E9A0A for ; Mon, 14 Apr 2008 17:57:22 +0200 (CEST) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id 49423BD41 for ; Mon, 14 Apr 2008 17:56:23 +0200 (CEST) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: duplicate primary index in bayes db from SpamAssassin Date: Mon, 14 Apr 2008 17:57:11 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4983835.7u2eeIJzQp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200804141757.21574@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.022 tagged_above=0 required=5 tests=AWL=0.022 X-Spam-Level: X-Archive-Number: 200804/120 X-Sequence-Number: 28884 --nextPart4983835.7u2eeIJzQp Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear list, I don't know whether pgsql-admin or the SA list is the=20 correct one to ask, so I start here. I have a bayes Postgres database=20 for SpamAssassin, which I use shared from 2 servers to have the same=20 content. I think this could be a locking issue or whatever, I don't=20 care. BUT: I have lots of "duplicate index" elements now, preventing a=20 restore or cleanup. Here's the dump and diff if anyone cares: http://zmi.at/x/bayes_dup_idx.dump.bz2 (upload currently running) http://zmi.at/x/bayes_dup_idx.diff.bz2 Could the problem be caused by any settings to the DB, or because of the=20 stored procedures? Normally there should be no way this can happen, so=20 what can cause this? mfg zmi =2D-=20 // 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 --nextPart4983835.7u2eeIJzQp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBIA37hzhSR9xwSCbQRAosAAJ9ssydP1DfhJf5JcYtnN2PLVVcA9gCfTpbU t0WewrClcT7p/3jq/8wBXsk= =ghrp -----END PGP SIGNATURE----- --nextPart4983835.7u2eeIJzQp--