Re: Rename synchronous_standby_names?

From: Vik Fearing <vik(at)2ndquadrant(dot)fr>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rename synchronous_standby_names?
Date: 2016-06-03 08:52:31
Message-ID: 5751454F.6020607@2ndquadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/06/16 02:49, Michael Paquier wrote:
> On Wed, Jun 1, 2016 at 3:56 AM, David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>> On Tue, May 31, 2016 at 2:19 PM, Peter Eisentraut
>> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>>>
>>> On 5/31/16 1:47 PM, Jaime Casanova wrote:
>>>>
>>>> Are we going to change synchronous_standby_names? Certainly the GUC is
>>>> not *only* a list of names anymore.
>>>>
>>>> synchronous_standby_config?
>>>> synchronous_standbys (adjust to correct english if necesary)?
>>>
>>> If the existing values are still going to be accepted, then I would leave
>>> it as is.
>>
>> +1
>
> +1. We've made quite a lot of deal to take an approach for the N-sync
> that is 100% backward-compatible, it would be good to not break that
> effort.

We could always accept it like we do for archive/hot_standby->replica.

I like synchronous_standby_config, so I vote for changing it.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Korbin Hoffman 2016-06-03 10:58:31 hstore: add hstore_length function
Previous Message Tatsuo Ishii 2016-06-03 08:46:42 Re: Statement timeout