Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id D61891A10764 for ; Thu, 10 Nov 2011 12:02:11 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 47867-08 for ; Thu, 10 Nov 2011 16:02:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 85A901245B60 for ; Thu, 10 Nov 2011 12:02:05 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Thu, 10 Nov 2011 10:02:04 -0600 Message-Id: <4EBBA11A0200002500042CCA@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Thu, 10 Nov 2011 10:02:02 -0600 From: "Kevin Grittner" To: "Thorsten Strufe" , Subject: Re: lost tablespace References: <4EBBAF18.7080102@googlemail.com> In-Reply-To: <4EBBAF18.7080102@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-3.101 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-1.201 X-Spam-Level: X-Archive-Number: 201111/50 X-Sequence-Number: 38644 Thorsten Strufe wrote: > is there any (sane) way to simply get postgre to entirely forget > about the broken db - and that's it (dumping the other db and > loading it back might not be the best solution, since it's rather > large..)? I think that using pg_dump for the good databases is sane, and the simplest solution. Another option would normally be one of the trigger-based replication systems, like Slony (to reduce down time to a matter of minutes or seconds); but the crippled state of the cluster may make the hard. http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling -Kevin