Horton

Re: issue with synchronized_standby_slots

Shlok Kyal <shlok.kyal.oss@gmail.com>

View thread
From: Shlok Kyal <shlok.kyal.oss@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Fabrice Chapuis <fabrice636861@gmail.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, Rahila Syed <rahilasyed90@gmail.com>, Alexander Kukushkin <cyberdemn@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Amit Kapila <amit.kapila16@gmail.com>
Date: 2025-10-23T09:28:11Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix GUC check_hook validation for synchronized_standby_slots.

  2. Make invalid primary_slot_name follow standard GUC error reporting.

Attachments

On Thu, 23 Oct 2025 at 13:45, Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> Dear Shlok,
>
> Thanks for updating the patch! Few comments.
>
> 1.
> You must separate patch for master and PG18, because ReplicationSlotValidateNameInternal()
> does not accept `bool allow_reserved_name` in the version.
>
> 2.
> Also, test for PG18 should not have the case which rejects the reserved name.
>
> 3.
> ```
> -- Parallel worker does not throw error during startup.
> SET min_parallel_table_scan_size TO 0;
> SET parallel_setup_cost TO 0;
> SET parallel_tuple_cost TO 0;
> ```
>
> According to contrib/pg_stat_statements/sql/parallel.sql, max_parallel_workers_per_gather
> should be also set. There is a possiblity that `make installcheck` is used and
> it has max_parallel_workers_per_gather=0.
>
> 4.
> ```
>         foreach_ptr(char, name, *elemlist)
> ```
>
> You can add a comment atop here like:
> Iterate the list to validate each slot name.
>
Hi Kuroda-san,
Thanks for reviewing the patches.
I have addressed the comments and attached the updated version.

Thanks,
Shlok Kyal