Re: Add id's to various elements in protocol.sgml
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Brar Piening <brar@gmx.de>, Chapman Flack <chap@anastigmatix.net>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-02T09:37:36Z
Lists: pgsql-hackers
On 01.03.22 20:50, Brar Piening wrote: > Patch is attached. I don't think it should get applied this way, though. > The fact that you only get links for section headers that have manually > assigned ids would be pretty surprising for users of the docs and in > some files (e.g. protocol-flow.html) only every other section has a > manually assigned id. It would be easy to emit a message (or even fail) > whenever the template fails to find an id and then manually assign ids > until they are everywhere (currently that means all varlistentries and > sections) but that would a) be quite some work and b) make the patch > quite heavy, so I wouldn't even start this before there is really > consensus that this is the right direction. I have applied the part of your patch that adds the id's. The discussion about the formatting aspect can continue. I changed the id's for the protocol messages to mixed case, so that it matches how these are commonly referred to elsewhere. It doesn't affect the output.
Commits
-
Add id's to various elements in protocol.sgml
- e58791c6ad31 15.0 landed
-
Improve parallel vacuum implementation.
- 22bd3cbe0c28 15.0 cited