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

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Marcos Pegoraro <marcos@f10.com.br>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-19T19:10:56Z
Lists: pgsql-hackers
On Fri, Dec 19, 2025 at 11:56 AM Marcos Pegoraro <marcos@f10.com.br> wrote:

> Em seg., 15 de dez. de 2025 às 09:19, Laurenz Albe <
> laurenz.albe@cybertec.at> escreveu:
>
>> Apart from the effort of the change, there is also the increased effort of
>> backpatching documentation changes, and those efforts have to be
>> outbalanced
>> by the benefits.
>>
>
> Are you sure we need to backpatch all these changes ?
> I'm not talking about the job I'll have but the job the committer will
> have.
> There are almost 300 different section numbers and more than 700 places
> will be changed,
> so will be 700 multiplied by how many versions of it. Are you sure ?
>
> I changed 8 or 10 just for testing and sending two as an example, just to
> see if it's worthwhile.
> Environment Variables need to change source and target, 30 places.
> String constants just source part, easy to change but harder to verify all
> related parts.
>
>
These changes aren't going to be back-patched.  The concern stated is that
given all the places being touched, the odds of future back-patches hitting
one of them and resulting in a conflict has increased substantially.

David J.