Re: Remove unnecessary secondary index terms for replication settings

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Remove unnecessary secondary index terms for replication settings
Date: 2025-04-23 21:09:45
Message-ID: 8425ab63-ee04-4ad5-8857-5806e3f4e751@app.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
EDB https://www.enterprisedb.com/

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2025-04-24 09:48:25 Documentation correction suggestion for primary key hashing on partitioned tables
Previous Message Fujii Masao 2025-04-23 06:53:54 Remove unnecessary secondary index terms for replication settings