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 7D0BB9FB207 for ; Tue, 19 Sep 2006 12:42:01 -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 07720-03 for ; Tue, 19 Sep 2006 15:41:47 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail733.megamailservers.com (mail733.megamailservers.com [69.49.98.43]) by postgresql.org (Postfix) with ESMTP id 02BCE9FB1EF for ; Tue, 19 Sep 2006 12:41:46 -0300 (ADT) X-Authenticated-User: paul.a.pnlassociates.com Received: from [69.3.2.106] (h-69-3-2-106.mclnva23.covad.net [69.3.2.106]) (authenticated bits=0) by mail733.megamailservers.com (8.13.6/8.13.1) with ESMTP id k8JFfeir014269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Sep 2006 11:41:43 -0400 Message-ID: <45100FB3.8020602@pnlassociates.com> Date: Tue, 19 Sep 2006 11:41:39 -0400 From: "Paul B. Anderson" User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Vacuum error on database postgres References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> <27602.1158238299@sss.pgh.pa.us> In-Reply-To: <27602.1158238299@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------030401020402020000010802" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.375 tagged_above=0 required=5 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200609/200 X-Sequence-Number: 23114 This is a multi-part message in MIME format. --------------030401020402020000010802 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Here are a couple of new data points on this issue. Deleting all records in pg_statistic and then reindexing clears the problem but I've had the problem in two of my own databases in two separate postgresql instances as well as the postgres database in both instances. I have a cluster of machines and the databases are on shared disk storage. I'm just getting this arrangement working and, while I've been debugging my scripts, I've accidentally had two copies of postgresql running against the same initdb directories at the same time on two different machines. Needless to say, this causes problems and I'm thinking that vacuuming in this condition may be at or near the root of the problem. Paul Tom Lane wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > . > > --------------030401020402020000010802 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Here are a couple of new data points on this issue. 

Deleting all records in pg_statistic and then reindexing clears the problem but I've had the problem in two of my own databases in two separate postgresql instances as well as the postgres database in both instances.

I have a cluster of machines and the databases are on shared disk storage.  I'm just getting this arrangement working and, while I've been debugging my scripts, I've accidentally had two copies of postgresql running against the same initdb directories at the same time on two different machines.  Needless to say, this causes problems and I'm thinking that vacuuming in this condition may be at or near the root of the problem.

Paul


Tom Lane wrote:
andy <andy@squeakycode.net> 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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly

.

  
--------------030401020402020000010802--