Hello,
Just looking at how the 2 differnt methods can be used to set the s_s_names
value.
1. For a simple case where quorum is required for a single group the JSON
could be:
{
"sync_standby_names":
{
"quorum":2,
"nodes":
[ "node1","node2","node3" ]
}
}
or
{
"sync_standby_names":
{
"quorum":2,
"group": "cluster1"
},
"groups":
{
"cluster1":["node1","node2","node3"]
}
}
Language:
2(node1, node2, node3)
2. For having quorum between different groups and node:
{
"sync_standby_names":
{
"quorum":2,
"nodes":
[
{"priority":1,"nodes":["node0"]},
{"quorum":2,"group": "cluster1"}
]
},
"groups":
{
"cluster1":["node1","node2","node3"]
}
}
or
{
"sync_standby_names":
{
"quorum":2,
"nodes":
[
{"priority":1,"group": "cluster2"},
{"quorum":2,"group": "cluster1"}
]
},
"groups":
{
"cluster1":["node1","node2","node3"],
"cluster2":["node0"]
}
}
Language:
2 (node0, cluster1: 2(node1, node2, node3))
Since there will not be many nesting and grouping, I still prefer new
language to JSON.
I understand one can easily, modify/add groups in JSON using in built
functions but I think changes will not be done too often.
-----
Beena Emerson
--
View this message in context:
http://postgresql.nabble.com/Support-for-N-synchronous-standby-servers-take-2-tp5849384p5860197.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
