On Fri, Mar 1, 2024 at 11:41 AM Masahiko Sawada <sawada.m...@gmail.com> wrote: > > On Fri, Mar 1, 2024 at 12:42 PM Zhijie Hou (Fujitsu) > <houzj.f...@fujitsu.com> wrote: > --- > I was a bit surprised by the fact that standby_slot_names value is > handled in a different way than a similar parameter > synchronous_standby_names. For example, the following command doesn't > work unless there is a replication slot 'slot1, slot2': > > =# alter system set standby_slot_names to 'slot1, slot2'; > ERROR: invalid value for parameter "standby_slot_names": ""slot1, slot2"" > DETAIL: replication slot "slot1, slot2" does not exist > > Whereas "alter system set synchronous_standby_names to stb1, stb2;" > can correctly separate the string into 'stb1' and 'stb2'. > > Probably it would be okay since this behavior of standby_slot_names is > the same as other GUC parameters that accept a comma-separated string. > But I was confused a bit the first time I used it. >
I think it is better to keep the behavior in this regard the same as 'synchronous_standby_names' because both have similarities w.r.t replication. -- With Regards, Amit Kapila.
