Re: Remove unnecessary secondary index terms for replication settings

From: Robert Treat <rob(at)xzilla(dot)net>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Remove unnecessary secondary index terms for replication settings
Date: 2025-04-24 14:30:26
Message-ID: CABV9wwOaN5EDtkUSaOib=C7kf2TQd9aJJBy0DeCoaDBFS49JoQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, Apr 23, 2025 at 2:54 AM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)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.

Robert Treat
https://xzilla.net

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Robert Treat 2025-04-24 15:13:24 Re: generated constraint name
Previous Message PG Doc comments form 2025-04-24 09:48:25 Documentation correction suggestion for primary key hashing on partitioned tables