Horton

Thread

Commits

  1. doc: Add missing <varlistentry> markups for developer GUCs

  1. docs: add missing <varlistentry> id elements for developer GUCs

    Ian Lawrence Barwick <barwick@gmail.com> — 2022-12-03T06:58:19Z

    Hi

A few of the developer option GUCs were missing the "id" attribute
in their markup, making it impossible to link to them directly.

Specifically the entries from "trace_locks" to "log_btree_build_stats" here:

    https://www.postgresql.org/docs/current/runtime-config-developer.html

Patch applies cleanly back to REL_11_STABLE.

Regards

Ian Barwick

  2. Re: docs: add missing <varlistentry> id elements for developer GUCs

    Michael Paquier <michael@paquier.xyz> — 2022-12-05T02:24:58Z

    On Sat, Dec 03, 2022 at 03:58:19PM +0900, Ian Lawrence Barwick wrote:
> A few of the developer option GUCs were missing the "id" attribute
> in their markup, making it impossible to link to them directly.

True enough that the other developer GUCs do that, so applied and
backpatched down to 11.
--
Michael

  3. Re: docs: add missing <varlistentry> id elements for developer GUCs

    Ian Lawrence Barwick <barwick@gmail.com> — 2022-12-06T00:59:34Z

    2022年12月5日(月) 11:25 Michael Paquier <michael@paquier.xyz>:
>
> On Sat, Dec 03, 2022 at 03:58:19PM +0900, Ian Lawrence Barwick wrote:
> > A few of the developer option GUCs were missing the "id" attribute
> > in their markup, making it impossible to link to them directly.
>
> True enough that the other developer GUCs do that, so applied and
> backpatched down to 11.

Thanks :).

It has since been brought to my attention that there's a general patch covering
missing "id" attributes, including those ones (see [1]), albeit
without a CF entry.
I will see if we can move that forward, before I end up sending in more
piecemeal patches as I encounter them...

[1] https://www.postgresql.org/message-id/flat/3bac458c-b121-1b20-8dea-0665986faa40%40gmx.de#f52d07e7782b893a54e6e31b5a20b4db

Regards

Ian Barwick