X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 205049FA2EA for ; Thu, 14 Sep 2006 09:51:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 51356-10 for ; Thu, 14 Sep 2006 12:51:41 +0000 (UTC) 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 261D09FA15C for ; Thu, 14 Sep 2006 09:51:41 -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 k8ECpdOd027603; Thu, 14 Sep 2006 08:51:39 -0400 (EDT) To: andy cc: pgsql-admin@postgresql.org Subject: Re: Vacuum error on database postgres In-reply-to: References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> Comments: In-reply-to andy message dated "Tue, 12 Sep 2006 21:20:55 -0500" Date: Thu, 14 Sep 2006 08:51:39 -0400 Message-ID: <27602.1158238299@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/127 X-Sequence-Number: 23041 andy writes: > So I'm ok, but I tried it again, by dropping the database and re-running > both scripts and got the same error again. So thought I'd offer a test > case if there was interest. Absolutely. I've seen just enough of these reports to make me think there's an underlying bug. regards, tom lane