Skip site navigation (1) Skip section navigation (2)

Re: Core team statement on replication in PostgreSQL

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 (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-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

In response to

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2008-05-29 16:48:56
Subject: Duplicate Key Error from ANALYZE
Previous:From: Aidan Van DykDate: 2008-05-29 16:35:41
Subject: Re: Core team statement on replication in PostgreSQL

pgsql-advocacy by date

Next:From: Shane AmblerDate: 2008-05-29 17:11:08
Subject: Re: Core team statement on replication in PostgreSQL
Previous:From: Aidan Van DykDate: 2008-05-29 16:35:41
Subject: Re: Core team statement on replication in PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group