Re: issue with synchronized_standby_slots - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: issue with synchronized_standby_slots
Date
Msg-id CAE9k0Pm9BixgN3H+vhnfsj27XkQi1JJ6nqp+rKq9En5o4JS-Rg@mail.gmail.com
Whole thread Raw
In response to Re: issue with synchronized_standby_slots  (Rahila Syed <rahilasyed90@gmail.com>)
List pgsql-hackers
On Wed, Sep 10, 2025 at 3:33 PM Rahila Syed <rahilasyed90@gmail.com> wrote:
>
> Hi,
>
>
>>  As for the synchronized_standby_slots, we can follow the behavior
>> similar to check_synchronous_standby_names and just give parsing
>> ERRORs. Any non-existent slot related errors can be given when that
>> parameter is later used.
>>
>> --
>
>
> Please find attached a patch that implements this. I will work on adding a test for it.
>

I suggest removing validate_sync_standby_slots() entirely since there
isn’t much left in it.

The below logic currently in validate_sync_standby_slots() to parse
the list of slots can be directly moved into
check_synchronized_standby_slots().

/* Verify syntax and parse string into a list of identifiers */
ok = SplitIdentifierString(rawname, ',', elemlist);

if (!ok)
GUC_check_errdetail("List syntax is invalid.");

--
With Regards,
Ashutosh Sharma.



pgsql-hackers by date:

Previous
From: Alastair Turner
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Shlok Kyal
Date:
Subject: Re: issue with synchronized_standby_slots