| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Douglas McNaught <doug(at)mcnaught(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Core team statement on replication in PostgreSQL |
| Date: | 2008-05-29 16:40:14 |
| Message-ID: | 594.1212079214@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Dave Page wrote:
>> Yes, we're talking real-time streaming (synchronous) log shipping.
> That's not what Tom's email said, AIUI.
Sorry, I was a bit sloppy about that. If we go with a WAL-shipping
solution it would be pretty easy to support both synchronous and
asynchronous cases (synchronous == master doesn't report commit until
the WAL is down to disk on the slaves too). There are different
use-cases for both so it'd make sense to do both.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shane Ambler | 2008-05-29 17:11:08 | Re: Core team statement on replication in PostgreSQL |
| Previous Message | Aidan Van Dyk | 2008-05-29 16:35:41 | Re: Core team statement on replication in PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2008-05-29 16:48:56 | Duplicate Key Error from ANALYZE |
| Previous Message | Aidan Van Dyk | 2008-05-29 16:35:41 | Re: Core team statement on replication in PostgreSQL |