Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hpe(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality
Date: 2016-04-14 14:41:30
Message-ID: CAHGQGwELxYQDtqyhLSMXHxbmdtRBXCqTdKt08_-KfZvQnji_yA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 14, 2016 at 11:22 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Apr 14, 2016 at 9:51 PM, Nicholson, Brad (Toronto, ON, CA)
> <bnicholson(at)hpe(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-04-14 17:11:43 Re: Bus error in pg_logical_slot_get_changes (9.4.7, sparc)
Previous Message Tom Lane 2016-04-14 14:26:37 Re: BUG #14084: typo in LIMIT documentation