Hello, Continuing testing: For pg_syncinfo.conf below an error is thrown.
{ "sync_info": { "quorum": 3, "nodes": [ {"priority":1,"group":"cluster1"}, "A" ] }, "groups": { "cluster1":["B","C"] } } LOG: database system is ready to accept connections LOG: autovacuum launcher started TRAP: FailedAssertion("!(n < list->length)", File: "list.c", Line: 392) LOG: server process (PID 17764) was terminated by signal 6: Aborted LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. LOG: all server processes terminated; reinitializing LOG: database system was interrupted; last known up at 2015-09-15 17:15:35 IST In the scenario here the quorum specified is 3 but there are just 2 nodes, what should the expected behaviour be? I feel the json parsing should throw an appropriate error with explanation as the sync rule does not make sense. The behaviour that the master keeps waiting for the non existent 3rd quorum node will not be helpful anyway. regards Sameer -- View this message in context: http://postgresql.nabble.com/Support-for-N-synchronous-standby-servers-take-2-tp5849384p5865954.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