From: | Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr> |
---|---|
To: | cho <tobutaz(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Cluster/Replication |
Date: | 2007-10-22 09:44:25 |
Message-ID: | 471C70F9.7060407@megafon.hr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | yogesh | 2007-10-22 12:03:52 | Re: Postgres SQL with Suse Linux |
Previous Message | Ewald Geschwinde | 2007-10-22 09:05:55 | Re: Cluster/Replication |