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 90C619FB1D3 for ; Tue, 19 Sep 2006 13:20:40 -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 27083-06 for ; Tue, 19 Sep 2006 16:20:31 +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 B0B7E9F9FB1 for ; Tue, 19 Sep 2006 13:20:30 -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 k8JGKRPh006966; Tue, 19 Sep 2006 12:20:27 -0400 (EDT) To: "Paul B. Anderson" cc: pgsql-admin@postgresql.org 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> <27602.1158238299@sss.pgh.pa.us> <45100FB3.8020602@pnlassociates.com> Comments: In-reply-to "Paul B. Anderson" message dated "Tue, 19 Sep 2006 11:41:39 -0400" Date: Tue, 19 Sep 2006 12:20:27 -0400 Message-ID: <6965.1158682827@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/201 X-Sequence-Number: 23115 "Paul B. Anderson" 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