Re: New standby_slot_names GUC in PG 17
От | Amit Kapila |
---|---|
Тема | Re: New standby_slot_names GUC in PG 17 |
Дата | |
Msg-id | CAA4eK1+mvBpoKPz-3Td6LFUy6EHbouC300Te7-6iSui6tcBK+Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New standby_slot_names GUC in PG 17 (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>) |
Ответы |
Re: New standby_slot_names GUC in PG 17
Re: New standby_slot_names GUC in PG 17 |
Список | 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 по дате отправления: