Re: Remove unnecessary secondary index terms for replication settings
От | Fujii Masao |
---|---|
Тема | Re: Remove unnecessary secondary index terms for replication settings |
Дата | |
Msg-id | e62e9e3a-4ec4-4297-a39c-3ca2ad72789b@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: Remove unnecessary secondary index terms for replication settings (Robert Treat <rob@xzilla.net>) |
Список | pgsql-docs |
On 2025/04/24 23:30, Robert Treat wrote: > On Wed, Apr 23, 2025 at 2:54 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: >> >> Hi, >> >> In config.sgml, the entries for max_replication_slots and >> max_active_replication_origins include secondary index terms: >> >> <primary><varname>max_replication_slots</varname> configuration parameter</primary> >> <secondary>in a sending server</secondary> >> >> <primary><varname>max_active_replication_origins</varname> configuration parameter</primary> >> <secondary>in a subscriber</secondary> >> >> These secondary terms don't seem necessary anymore, since each parameter >> now has only one index entry. Removing them would simplify the documentation. >> >> Originally, the secondary entries made sense because >> max_active_replication_origins was part of max_replication_slots, >> so both needed separate index entries. But commit 04ff636cbce >> split them into distinct parameters. >> >> Patch attached. >> > > Make sense, +1 from me. Thanks both for the review! I've pushed the patch. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
В списке pgsql-docs по дате отправления: