pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul B. Anderson <paul.a@pnlassociates.com>
To: pgsql-admin@postgresql.org
Subject: Re: Vacuum error on database postgres
Date: Tue, 19 Sep 2006 11:41:39 -0400
Message-ID: <45100FB3.8020602@pnlassociates.com> (raw)
In-Reply-To: <27602.1158238299@sss.pgh.pa.us>
References: <44F82150.5000809@pnlassociates.com>
	<4001.1157121669@sss.pgh.pa.us>
	<ee7pua$2bou$1@news.hub.org>
	<27602.1158238299@sss.pgh.pa.us>

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
>
> .
>
>   

view thread (21+ messages)  latest in thread

Message-ID: <45100FB3.8020602@pnlassociates.com>
Permalink:  ../45100FB3.8020602@pnlassociates.com/
Also on:    postgresql.org/message-id/45100FB3.8020602@pnlassociates.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: paul.a@pnlassociates.com
  Subject: Re: Vacuum error on database postgres
  In-Reply-To: <45100FB3.8020602@pnlassociates.com>
  References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> <ee7pua$2bou$1@news.hub.org> <27602.1158238299@sss.pgh.pa.us> <45100FB3.8020602@pnlassociates.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox