Re: Standalone synchronous master - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Standalone synchronous master
Date
Msg-id 52D077CC.6090308@commandprompt.com
Whole thread Raw
In response to Re: Standalone synchronous master  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Standalone synchronous master  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 01/10/2014 02:33 PM, Andres Freund wrote:
>
> On 2014-01-10 14:29:58 -0800, Joshua D. Drake wrote:
>> db02 goes down. It doesn't matter why. It is down. db01 continues to accept
>> orders, allow people to log into the website and we can still service
>> accounts. The continuity of service continues.
>
> Why is that configuration advantageous over a async configuration is the
> question. Why, with those requirements, are you using a synchronous
> standby at all?

If the master goes down, I can fail over knowing that as many of my 
transactions as possible have been replicated.

JD




-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
"In a time of universal deceit - telling the truth is a revolutionary 
act.", George Orwell



pgsql-hackers by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Standalone synchronous master
Next
From: Andres Freund
Date:
Subject: Re: Standalone synchronous master