| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Garber, Mikhail" <mgarber(at)amazon(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Chris Browne" <cbbrowne(at)acm(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: replication in Postgres |
| Date: | 2007-11-26 21:48:23 |
| Message-ID: | dcc563d10711261348n3d3033f0o3de9cd796381bd6c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Nov 26, 2007 3:41 PM, Garber, Mikhail <mgarber(at)amazon(dot)com> wrote:
>
> So what is the state-of-the-art in the Postgresql world if I _do_ want synchronous replication? 2-phase commit from the client application? Any success/horror stories about doing it in Java?
Depending on the restrictions you're willing to live with, pgpool may
be a good choice, and it is dirt simple to implement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-11-26 22:12:20 | Re: Primary Key |
| Previous Message | Garber, Mikhail | 2007-11-26 21:41:50 | Re: replication in Postgres |