X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E42E49FB548 for ; Fri, 1 Sep 2006 12:38:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 98920-05 for ; Fri, 1 Sep 2006 12:37:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A5B519FB4A7 for ; Fri, 1 Sep 2006 11:41:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k81Ef9fJ004002; Fri, 1 Sep 2006 10:41:09 -0400 (EDT) To: "Paul B. Anderson" cc: "[ADMIN]" Subject: Re: Vacuum error on database postgres In-reply-to: <44F82150.5000809@pnlassociates.com> References: <44F82150.5000809@pnlassociates.com> Comments: In-reply-to "Paul B. Anderson" message dated "Fri, 01 Sep 2006 08:02:24 -0400" Date: Fri, 01 Sep 2006 10:41:09 -0400 Message-ID: <4001.1157121669@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.128 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/5 X-Sequence-Number: 22919 "Paul B. Anderson" writes: > I did delete exactly one of each of these using ctid and the query then > shows no duplicates. But, the problem comes right back in the next > database-wide vacuum. That's pretty odd --- I'm inclined to suspect index corruption. > I also tried reindexing the table. Get rid of the duplicates (actually, I'd just blow away all the pg_statistic entries for each of these tables) and *then* reindex. Then re-analyze and see what happens. Worst case you could just delete everything in pg_statistic, reindex it, do a database-wide ANALYZE to repopulate it. By definition there's not any original data in that table... regards, tom lane