Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality
От | Fujii Masao |
---|---|
Тема | Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality |
Дата | |
Msg-id | CAHGQGwELxYQDtqyhLSMXHxbmdtRBXCqTdKt08_-KfZvQnji_yA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 9.6 synchronous_standby_names: discrepancy between docs and functionality (Michael Paquier <michael.paquier@gmail.com>) |
Список | 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 по дате отправления: