From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Synchronization levels in SR |
Date: | 2010-05-26 13:54:46 |
Message-ID: | 1274882086.6203.3042.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2010-05-26 at 07:10 -0400, Robert Haas wrote:
> OK. In words of one syllable, your way still has all the same knobs,
> plus some more.
I explained how the per-standby settings would take many parameters,
whereas per-transaction settings take far fewer.
> You sketched out a design which still had a per-standby setting for
> each standby, but IN ADDITION had a setting for a setting to control
> quorum commit[1].
No, you misread it. Again. The parameters were not IN ADDITION -
obviously so, otherwise I wouldn't claim there were fewer, would I?
Your reply has again avoided the subject of how we would handle failure
modes with per-standby settings. That is important.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-05-26 13:54:49 | Re: out-of-date comment in CreateRestartPoint() |
Previous Message | Tom Lane | 2010-05-26 13:50:02 | Re: ExecutorCheckPerms() hook |