Re: Support for N synchronous standby servers - take 2 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support for N synchronous standby servers - take 2
Date
Msg-id 5593FF60.6020003@gmx.net
Whole thread Raw
In response to Re: Support for N synchronous standby servers - take 2  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 6/26/15 1:12 PM, Josh Berkus wrote:
> If we're going to do quorum, multi-set synchrep, then we need to have a
> real management interface.  Like, we really ought to have a system
> catalog and some built in functions to manage this instead, e.g.
> 
> pg_add_synch_set(set_name NAME, quorum INT, set_members VARIADIC)
> 
> pg_add_synch_set('bolivia', 1, 'bsrv-2,'bsrv-3','bsrv-5')
> 
> pg_modify_sync_set(quorum INT, set_members VARIADIC)
> 
> pg_drop_synch_set(set_name NAME)

I respect that some people might like this, but I don't really see this
as an improvement.  It's much easier for an administration person or
program to type out a list of standbys in a text file than having to go
through these interfaces that are non-idempotent, verbose, and only
available when the database server is up.  The nice thing about a plain
and simple system is that you can build a complicated system on top of
it, if desired.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: NULL passed as an argument to memcmp() in parse_func.c
Next
From: Simon Riggs
Date:
Subject: Re: drop/truncate table sucks for large values of shared buffers