| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Chander Ganesan" <chander(at)otg-nc(dot)com> |
| Cc: | "Madison Kelly" <linux(at)alteeve(dot)com>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: High-availability |
| Date: | 2007-06-05 06:12:20 |
| Message-ID: | 1181023941.2870.154.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2007-06-04 at 10:21 -0400, Chander Ganesan wrote:
> It's not too hard to put together a "warm standby" synchronous
> replication mechanism with overhead that isn't too much more than what
> you incur by enabling PITR... Such systems can also have very fast
> failover on failure detection (via heartbeat2), and be synchronous.
Do you have any performance measurements of either the replication
overhead or the failover time? I'm interested in how well we cope with
high transaction rates. Thanks.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-06-05 06:35:06 | Re: There can be only one! How to avoid the "highlander-problem". |
| Previous Message | Erick Papadakis | 2007-06-05 05:46:42 | Database design wisdom needed |