From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sync Replication with transaction-controlled durability |
Date: | 2010-10-08 15:10:11 |
Message-ID: | 1286550611.2304.958.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2010-09-14 at 18:48 +0100, Simon Riggs wrote:
> I'm working on a patch to implement synchronous replication for
> PostgreSQL, with user-controlled durability specified on the master. The
> design also provides high throughput by allowing concurrent processes to
> handle the WAL stream. The proposal requires only 3 new parameters and
> takes into account much community feedback on earlier ideas.
I'm now implementing v5, which simplifies the parameters still further
USERSET on master
* synchronous_replication = off (default) | on
* synchronous_replication_timeout >=0 default=0 means wait forever
set in postgresql.conf on standby
* synchronous_replication_service = on (default) | off
WALwriter is not active, nor are multiple sync rep modes available.
Coding allows us to extend number of modes in future.
Coding also solves problem raised by Dimitri: we don't advertise the
sync rep service until the standby has caught up.
This patch is a rough WIP, mostly stripping out and streamlining. It
doesn't work yet, but people say they like to see me working, so here
'tis.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
Attachment | Content-Type | Size |
---|---|---|
syncrep5.1.patch.bz2 | application/x-bzip | 14.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wanner | 2010-10-08 15:12:49 | Re: Issues with Quorum Commit |
Previous Message | Markus Wanner | 2010-10-08 15:06:26 | Re: Issues with Quorum Commit |