Re: Sync Rep Design

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, greg(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sync Rep Design
Date: 2011-01-04 19:50:17
Message-ID: 4D2379F9.2000901@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/04/2011 07:51 PM, Simon Riggs wrote:
> On Tue, 2011-01-04 at 10:28 -0800, Josh Berkus wrote:
>
>> The relevant question is: which configuration(s) can we have ready for
>> the next CommitFest and alpha release?
>
> Based upon that series of conversations, I've reworked the design so
> that there is (currently) only a single standby offering sync rep at any
> one time. Other standbys can request to be sync standbys but they only
> become the sync standby if the first one fails. Which was simple to do
> and bridges the challenges of an exactly identified sync standby and the
> fragility of too closely specifying the config.

ah cool - like that approach for 9.1!

Thanks for working on that!

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-04 19:52:30 Re: WIP: Range Types
Previous Message Dimitri Fontaine 2011-01-04 19:48:46 Re: Upgrading Extension, version numbers