Remove unnecessary secondary index terms for replication settings

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: pgsql-docs@lists.postgresql.org
Date: 2025-04-23T06:53:54Z
Lists: pgsql-docs

Attachments

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.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Commits

  1. doc: remove unnecessary secondary index terms for replication settings.

  2. Add GUC option to control maximum active replication origins.