Re: Remove unnecessary secondary index terms for replication settings - Mailing list pgsql-docs

From Euler Taveira
Subject Re: Remove unnecessary secondary index terms for replication settings
Date
Msg-id 8425ab63-ee04-4ad5-8857-5806e3f4e751@app.fastmail.com
Whole thread Raw
In response to Remove unnecessary secondary index terms for replication settings  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-docs
On Wed, Apr 23, 2025, at 3:53 AM, Fujii Masao wrote:
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.

Agreed. It was an oversight in my patch. LGTM.


--
Euler Taveira

pgsql-docs by date:

Previous
From: Fujii Masao
Date:
Subject: Remove unnecessary secondary index terms for replication settings
Next
From: PG Doc comments form
Date:
Subject: Documentation correction suggestion for primary key hashing on partitioned tables