From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Thorsten Strufe <strufe.pub@googlemail.com>
To: pgsql-admin@postgresql.org
Subject: Re: lost tablespace
Date: Thu, 10 Nov 2011 10:02:02 -0600
Message-ID: <4EBBA11A0200002500042CCA@gw.wicourts.gov> (raw)
In-Reply-To: <4EBBAF18.7080102@googlemail.com>
References: <4EBBAF18.7080102@googlemail.com>
Thorsten Strufe <strufe.pub@googlemail.com> 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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, strufe.pub@googlemail.com
Subject: Re: lost tablespace
In-Reply-To: <4EBBA11A0200002500042CCA@gw.wicourts.gov>
* 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