X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 19F5AD1D321 for ; Tue, 27 Jan 2004 01:24:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17962-08 for ; Mon, 26 Jan 2004 21:23:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 0BF0ED1D27C for ; Mon, 26 Jan 2004 21:23:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0R1NdnX007742; Mon, 26 Jan 2004 20:23:39 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <002001c3e472$88698fd0$24976b80@amer.cisco.com> References: <002001c3e472$88698fd0$24976b80@amer.cisco.com> Comments: In-reply-to "Chris White (cjwhite)" message dated "Mon, 26 Jan 2004 17:11:45 -0800" Date: Mon, 26 Jan 2004 20:23:39 -0500 Message-ID: <7741.1075166619@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/247 X-Sequence-Number: 12110 "Chris White (cjwhite)" writes: > VACUUM: DEBUG sql sql sql DEBUG: Index pg_largeobject_loid_pn_index: > Pages 14; Tuples 1044: Deleted 232. > ... > VACUUM: WARNING sql sql sql ERROR: Cannot insert a duplicate key into > unique index pg_largeobject_loid_pn_index > When I run postgres with the -P and -O options to reindex the index, > everything seem to run okay, I see no error messages. However, when I > restart postmaster and try and do a vacuum again, I get the same error > messages. I don't think you can have reindexed the index. With only 1044 rows in it, it shouldn't take up more than 3 or 4 pages when freshly created; certainly not 14. Are you sure you reindexed in the right database? If you're sure it's not pilot error, let's see the exact transcript of what you did with the standalone postgres, and also the exact transcript (no "sql sql sql") of the failing VACUUM afterwards. Also, what PG version is this? regards, tom lane