| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, 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(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Standalone synchronous master |
| Date: | 2014-01-08 22:58:16 |
| Message-ID: | 52CDD808.5090302@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/08/2014 02:49 PM, Tom Lane wrote:
> Then you don't understand the point of sync mode, and you shouldn't be
> using it. The point is *exactly* to refuse to commit transactions unless
> we can guarantee the data's been replicated.
I understand exactly that and I don't disagree, except in the case where
it is going to bring down the master (see my further reply). I now
remember arguing about this a few years ago when we started down the
sync path.
Anyway, perhaps this is just something of a knob that can be turned. We
don't have to continue the argument. Thank you for considering what I
was saying.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-01-08 22:58:51 | Re: Standalone synchronous master |
| Previous Message | Stephen Frost | 2014-01-08 22:56:37 | Re: Standalone synchronous master |