From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Remove unnecessary secondary index terms for replication settings |
Date: | 2025-04-23 06:53:54 |
Message-ID: | e825e7a7-4877-441d-93c1-25377db36c31@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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
Attachment | Content-Type | Size |
---|---|---|
v1-0001-doc-remove-unnecessary-secondary-index-terms-for-.patch | text/plain | 1.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2025-04-23 21:09:45 | Re: Remove unnecessary secondary index terms for replication settings |
Previous Message | David G. Johnston | 2025-04-22 13:47:42 | Re: Please clarify docs on user-defined settings for SET and RESET |