Re: Standalone synchronous master

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, MauMau <maumau307(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Standalone synchronous master
Date: 2014-01-10 22:29:58
Message-ID: 52D07466.6070005@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 01/10/2014 01:49 PM, Andres Freund wrote:
>>
>> I know I am the one that instigated all of this so I want to be very clear
>> on what I and what I am confident that my customers would expect.
>>
>> If a synchronous slave goes down, the master continues to operate. That is
>> all. I don't care if it is configurable (I would be fine with that). I don't
>> care if it is not automatic (e.g; slave goes down and we have to tell the
>> master to continue).
>
> Would you please explain, as precise as possible, what the advantages of
> using a synchronous standby would be in such a scenario?

Current behavior:

db01->sync->db02

Transactions are happening. Everything is happy. Website is up. Orders
are being made.

db02 goes down. It doesn't matter why. It is down. Because it is down,
db01 for all intents and purposes is also down because we are using sync
replication. We have just lost continuity of service, we can no longer
accept orders, we can no longer allow people to log into the website, we
can no longer service accounts.

In short, we are out of business.

Proposed behavior:

db01->sync->db02

Transactions are happening. Everything is happy. Website is up. Orders
are being made.

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.

Yes, there are all kinds of things that need to be considered when that
happens, that isn't the point. The point is, PostgreSQL continues its
uptime guarantee and allows the business to continue to function as (if)
nothing has happened.

For many and I dare say the majority of businesses, this is enough. They
know that if the slave goes down they can continue to operate. They know
if the master goes down they can fail over. They know that while both
are up they are using sync rep (with various caveats). They are happy.
They like that it is simple and just works. They continue to use PostgreSQL.

Sincerely,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-01-10 22:33:55 Re: Standalone synchronous master
Previous Message Stephen Frost 2014-01-10 22:28:55 Re: Standalone synchronous master