From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: High Avaliable in the PostgreSQL.
Date: Wed, 30 May 2007 18:26:57 -0400
Message-ID: <20070530222657.GC17809@phlogiston.dyndns.org> (raw)
In-Reply-To: <1180563122.4265.2.camel@aleph.whitemice.org>
References: <20070530164208.2657ee91@localhost>
<20070530211833.GA17639@phlogiston.dyndns.org>
<1180563122.4265.2.camel@aleph.whitemice.org>
On Wed, May 30, 2007 at 06:12:02PM -0400, Adam Tauno Williams wrote:
>
> Sure it can be done. Get two SANs that support replication, redundant
> high-speed WAN links, high end servers, large UPSs, and generators.
Most SANs that I've seen aren't in "geographically separate"
locations in the way most think of this. It's usually metronet --
it's not even a different city. That's a poor disaster prevention
strategy, although it might be worth it as step one. (If you can
take the latency, of course, you can make this go further, but true
both-coast solutions, for instance, will make the latency such that
users will certainly be able to see it.)
A
--
Andrew Sullivan | ajs@crankycanuck.ca
However important originality may be in some fields, restraint and
adherence to procedure emerge as the more significant virtues in a
great many others. --Alain de Botton
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: ajs@crankycanuck.ca
Subject: Re: High Avaliable in the PostgreSQL.
In-Reply-To: <20070530222657.GC17809@phlogiston.dyndns.org>
* 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