Re: Vacuum error on database postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Paul B(dot) Anderson" <paul(dot)a(at)pnlassociates(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Vacuum error on database postgres
Date: 2006-09-19 16:20:27
Message-ID: 6965.1158682827@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

"Paul B. Anderson" <paul(dot)a(at)pnlassociates(dot)com> writes:
> 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.

You're going to have much worse problems than this from that. Two
postmasters modifying the same data files is a recipe for complete
corruption. I would recommend abandoning any database you realize
this has happened to: just initdb and start over. The chances of
being able to fix it are minimal.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Fernando Machado 2006-09-19 17:30:34 Multi-Master Async Replication
Previous Message Paul B. Anderson 2006-09-19 15:41:39 Re: Vacuum error on database postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2006-09-19 16:21:20 Re: advisory locks (was: 8.2 beta blockers)
Previous Message Chris Browne 2006-09-19 16:15:40 Re: vista