Re: Quorum commit for multiple synchronous replication. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Quorum commit for multiple synchronous replication.
Date
Msg-id CAB7nPqTrXrfrhNVJYcyB2r-6ZVnAzsHbf9_6ZCfi+EnkHeTYwg@mail.gmail.com
Whole thread Raw
In response to Quorum commit for multiple synchronous replication.  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Quorum commit for multiple synchronous replication.  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Wed, Aug 3, 2016 at 2:52 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> I was thinking that the syntax for quorum method would use '[ ... ]'
> but it will be confused with '( ... )' priority method used.
> 001 patch adds 'Any N ( ... )' style syntax but I know that we still
> might need to discuss about better syntax, discussion is very welcome.
> Attached draft patch, please give me feedback.

I am +1 for using either "{}" or "[]" to define a quorum set, and -1
for the addition of a keyword in front of the integer defining for how
many nodes server need to wait for.

-    foreach(cell, sync_standbys)
+    foreach (cell, sync_standbys)    {
-        WalSnd       *walsnd = &WalSndCtl->walsnds[lfirst_int(cell)];
+        WalSnd *walsnd = &WalSndCtl->walsnds[lfirst_int(cell)];
This patch has some noise.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Way to access LSN (for each transaction) by directly talking to postgres?
Next
From: Michael Paquier
Date:
Subject: Re: Way to access LSN (for each transaction) by directly talking to postgres?