From: Mario Splivalo <mario.splivalo@megafon.hr>
To: cho <tobutaz@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Cluster/Replication
Date: Mon, 22 Oct 2007 11:44:25 +0200
Message-ID: <471C70F9.7060407@megafon.hr> (raw)
In-Reply-To: <pan.2007.10.22.08.34.20@gmail.com>
References: <D7B69B79-A6B1-443B-AAB7-C53CA60BD874@eaglepress.com>
<pan.2007.10.22.08.34.20@gmail.com>
cho wrote:
> Le Fri, 19 Oct 2007 12:43:40 -0400, Sean Brown a écrit :
>
> Have a look at pgpool-I or pgpool-II in replication mode.
> Pgpool proxies SQL requests, so that requests on one server are replayed
> on the other. pgpool-I is limited to two nodes, whereas pgpool-II is not.
> Latency is important for write performance. You can do failover, you just
> need to detect by yourself when one node is dead.
>
> There is also PITR recovery, but as it batches the transaction logs you
> may lose a bit of data (up to a configured data size / duration).
>
>
PITR does not allow for the 'slave' server to be on-line, meaning you
can't do SELECTs on the slave while shipping WALs.
Mike
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: mario.splivalo@megafon.hr, tobutaz@gmail.com
Subject: Re: Cluster/Replication
In-Reply-To: <471C70F9.7060407@megafon.hr>
* 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