Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality - Mailing list pgsql-bugs

From Fujii Masao
Subject Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality
Date
Msg-id CAHGQGwELxYQDtqyhLSMXHxbmdtRBXCqTdKt08_-KfZvQnji_yA@mail.gmail.com
Whole thread Raw
In response to Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Thu, Apr 14, 2016 at 11:22 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Thu, Apr 14, 2016 at 9:51 PM, Nicholson, Brad (Toronto, ON, CA)
> <bnicholson@hpe.com> wrote:
>> When you try and use this example, it fails:
>>
>> syncrep=# alter system set synchronous_standby_names='2 (s1, s2, s3)';
>> ERROR:  invalid value for parameter "synchronous_standby_names": "2 (s1, s2, s3)"
>> DETAIL:  List syntax is invalid.

Maybe 9.6dev RPM that you installed was created before multiple
sync standbys feature was committed.

>> If you remove the space from between the 2 & the ( it works:
>>
>> syncrep=# alter system set synchronous_standby_names='2(s1, s2, s3)';
>> ALTER SYSTEM

Before multiple sync standbys feature was added, only comma-separated
list was valid in synchronous_standby_names. Since probably '2(s1, s2, s3)'
was interpreted as a comma-separated list of three standby names
"2(s1", "s2" and "s3)", it worked fine.

Regards,

--
Fujii Masao

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14084: typo in LIMIT documentation
Next
From: "Zombade, Prashant"
Date:
Subject: PostgreSQL on Korean Windows Server 2008 R2 Standard