pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: Real time replication of PG DBs accross two servers - any experiences?
Date: Wed, 14 Apr 2004 11:12:57 +0200
Message-ID: <200404141112.57204.peter_e@gmx.net> (raw)
In-Reply-To: <m3isg36yke.fsf@wolfe.cbbrowne.com>
References: <407B85CF.4010404@kieser.net>
	<200404132052.12589.peter_e@gmx.net>
	<m3isg36yke.fsf@wolfe.cbbrowne.com>

Christopher Browne wrote:
> > To ensure high availability, using DRBD to replicate the storage or
> > using a shared storage (e.g., EMC^2) does the job.  That saves you
> > the trouble of having to set up and manage a database replication
> > solution at all.
>
> Regrettably, "disk replication" schemes aren't generally able to cope
> with keeping the database up and alive while replication is taking
> place.

The ones mentioned above certainly keep the database running at all 
times until a failover.

> You need to shut down the database that is attached to a
> "target/slave" system every time you "sync" the target/slave against
> the source/master.

The slave database doesn't run at all while the master is alive.

> But when the people paying for the duplicate set of hardware realize
> that it's sitting there "otherwise useless" at any time that there
> hasn't been a failure, they'll presumably agitate for some 'better'
> sort of replication...

If you can set up a true database-level replication system that does 
something useful with the slave server while the master is running 
(i.e., load balancing) for the same price (hardware + labor + 
post-installation service) that you (or I or someone) can set up a disk 
replication system for then it would be interesting.  So far I haven't 
seen it happening.  In my experience, load balancing is not needed in 
most cases, so no one is going to bother paying for the extra 
functionality that they don't need.

The other advantage of disk replication is that you can secure almost 
any service in that same way (web, dns, ldap, etc.), so the management 
and setup effort spent on any particular service diminishes.




view thread (8+ messages)  latest in thread

Message-ID: <200404141112.57204.peter_e@gmx.net>
Permalink:  ../200404141112.57204.peter_e@gmx.net/
Also on:    postgresql.org/message-id/200404141112.57204.peter_e@gmx.net

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: peter_e@gmx.net, cbbrowne@acm.org
  Subject: Re: Real time replication of PG DBs accross two servers - any experiences?
  In-Reply-To: <200404141112.57204.peter_e@gmx.net>
  References: <407B85CF.4010404@kieser.net> <200404132052.12589.peter_e@gmx.net> <m3isg36yke.fsf@wolfe.cbbrowne.com> <200404141112.57204.peter_e@gmx.net>

* 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