Re: New standby_slot_names GUC in PG 17 - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: New standby_slot_names GUC in PG 17
Date
Msg-id CAA4eK1+mvBpoKPz-3Td6LFUy6EHbouC300Te7-6iSui6tcBK+Q@mail.gmail.com
Whole thread Raw
In response to Re: New standby_slot_names GUC in PG 17  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: New standby_slot_names GUC in PG 17
Re: New standby_slot_names GUC in PG 17
List pgsql-hackers
On Wed, Jun 26, 2024 at 10:19 AM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
>
>
> 2 ====
>
> Should we rename StandbySlotNamesConfigData too?
>

How about SyncStandbySlotsConfigData?

> 3 ====
>
> Should we rename SlotExistsInStandbySlotNames too?
>

Similarly SlotExistsInSyncStandbySlots?

> 4 ====
>
> Should we rename validate_standby_slots() too?
>

And validate_sync_standby_slots()?

--- a/doc/src/sgml/release-17.sgml
+++ b/doc/src/sgml/release-17.sgml
@@ -1325,7 +1325,7 @@ Author: Michael Paquier <michael@paquier.xyz>

 <!--
 Author: Amit Kapila <akapila@postgresql.org>
-2024-03-08 [bf279ddd1] Introduce a new GUC 'standby_slot_names'.
+2024-03-08 [bf279ddd1] Introduce a new GUC 'synchronized_standby_slots'.

I am not sure if it is a good idea to change release notes in the same
commit as the code change. I would prefer to do it in a separate
commit.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Improve the connection failure error messages
Next
From: Michael Paquier
Date:
Subject: Re: New standby_slot_names GUC in PG 17