| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Brar Piening <brar(at)gmx(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add id's to various elements in protocol.sgml |
| Date: | 2021-12-20 15:09:35 |
| Message-ID: | CA+Tgmoa=Dwg0HMz1V=1y175RE9xXguEEs9wJz-Jigw23qakWoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 17, 2021 at 6:54 PM Brar Piening <brar(at)gmx(dot)de> wrote:
> The purpose is that you can directly link to the id in the public html
> docs which still gets generated (e. g.
> https://www.postgresql.org/docs/14/protocol-replication.html#PROTOCOL-REPLICATION-BASE-BACKUP).
>
> Essentially it gives people discussing the protocol and pointing to a
> certain command or message format the chance to link to the very thing
> they are discussing instead of the top of the lengthy html page.
As a data point, this is something I have also wanted to do, from time
to time. I am generally of the opinion that any place the
documentation has a long list of things, which should add ids, so that
people can link to the particular thing in the list to which they want
to draw someone's attention.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-12-20 15:19:44 | Re: Refactoring of compression options in pg_basebackup |
| Previous Message | Tom Lane | 2021-12-20 15:09:25 | Re: Getting rid of regression test input/ and output/ files |