Re: [HACKERS] Multiple synchronous_standby_names rules - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Multiple synchronous_standby_names rules
Date
Msg-id CAB7nPqR4+LNv0jey+tRBFm1pXhjhGkik=U=rBBczKbkVcGT8GQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Multiple synchronous_standby_names rules  (James Sewell <james.sewell@jirotech.com>)
Responses Re: [HACKERS] Multiple synchronous_standby_names rules  (James Sewell <james.sewell@jirotech.com>)
List pgsql-hackers
On Thu, Jan 12, 2017 at 9:53 AM, James Sewell <james.sewell@jirotech.com> wrote:
> What is needed to support this is the ability to configure Px with something like:
>
>  1 (P1, P2, P3), 1 (D1, D2, D3)
>
> Would there be any appetite for this - or would it be seen as over complication of the current rules?

There have been discussions about being able to do that and there are
really use cases where that would be useful. As lately quorum commit
has been committed, we have a better idea of the grammar to use
(yeah!), though there are a couple of things remaining regarding the
design of node subsets:
- How to define group names? Making them mandatory would likely be the
way to go.
- How to represent that intuitively in pg_stat_replication? Perhaps
the answer here is an extra column in this system view.
-- 
Michael



pgsql-hackers by date:

Previous
From: James Sewell
Date:
Subject: [HACKERS] Multiple synchronous_standby_names rules
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] Retiring from the Core Team