Re: issue with synchronized_standby_slots - Mailing list pgsql-hackers

From Shlok Kyal
Subject Re: issue with synchronized_standby_slots
Date
Msg-id CANhcyEXKyF82yDqb34W-=snfwbBzmWjWe=UHt+Z7iCssiqdrsQ@mail.gmail.com
Whole thread Raw
In response to Re: issue with synchronized_standby_slots  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Fri, 24 Oct 2025 at 15:08, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Fri, Oct 24, 2025 at 1:24 PM Hayato Kuroda (Fujitsu)
> <kuroda.hayato@fujitsu.com> wrote:
> >
> > Dear Shlok,
> >
> > ```
> > -- Can set synchronized_standby_slots to a non-existent slot name.
> > ALTER SYSTEM SET synchronized_standby_slots='missing';
> > SELECT pg_reload_conf();
> >
> > -- Reset the GUC.
> > ALTER SYSTEM RESET synchronized_standby_slots;
> > SELECT pg_reload_conf();
> > ```
> >
> > pg_reload_conf() is called twice here but I'm not sure it is really needed.
> > ALTER SYSTEM itself can validate parameters via parse_and_validate_value(elevel=ERROR),
> > and pg_reload_conf() won't affect synchronously.
>
> I also think pg_reload_conf() won't be required here.
>
I agree that .pg_reload_conf() is not required. I have removed it in
the latest version of patches.

Thanks,
Shlok Kyal

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Should we say "wal_level = logical" instead of "wal_level >= logical"
Next
From: Ranier Vilela
Date:
Subject: Re: Avoid resource leak (src/test/regress/pg_regress.c)