Re: issue with synchronized_standby_slots

From: Rahila Syed <rahilasyed90(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, Fabrice Chapuis <fabrice636861(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: issue with synchronized_standby_slots
Date: 2025-09-10 10:02:58
Message-ID: CAH2L28uOFMhm-YSQNUVqZycSKoCbRsEsj0t3UEAEFu+RzbZ=jA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Thank you,
Rahila Syed

Attachment Content-Type Size
0001-Remove-the-validation-from-the-GUC-check-hook.patch application/octet-stream 2.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2025-09-10 10:14:25 Re: Eagerly evict bulkwrite strategy ring
Previous Message Amit Kapila 2025-09-10 09:55:37 Re: Proposal: Conflict log history table for Logical Replication