Re: Get rid of "Section.N.N.N" on DOCs

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Get rid of "Section.N.N.N" on DOCs
Date: 2025-12-14 17:35:17
Message-ID: CAKFQuwbM4V2cOj8Mq2rk7+HU6AS0BPkruhV_MZrqZLbBMg9s_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 14, 2025 at 10:30 AM Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:

> There are places where links are mixed, some of them are auto explanatory,
> some don't, like on See Also of VACUUM
> vacuumdb <https://www.postgresql.org/docs/18/app-vacuumdb.html>,
> Section 19.10.2
> <https://www.postgresql.org/docs/18/runtime-config-vacuum.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST>
> , Section 24.1.6
> <https://www.postgresql.org/docs/18/routine-vacuuming.html#AUTOVACUUM>,
> Section 27.4.5
> <https://www.postgresql.org/docs/18/progress-reporting.html#VACUUM-PROGRESS-REPORTING>
> , Section 27.4.2
> <https://www.postgresql.org/docs/18/progress-reporting.html#CLUSTER-PROGRESS-REPORTING>
>
> For that we need only put a "xreflabel" tag on that target link.
>
> I can create a patch for all of them, but I would like to know why it's
> done this way.
>

That would be great. I don't think it's intentional, just not everyone
knowing and thus failing to add the additional attribute.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2025-12-14 18:21:40 Re: Get rid of "Section.N.N.N" on DOCs
Previous Message Marcos Pegoraro 2025-12-14 17:30:07 Get rid of "Section.N.N.N" on DOCs