Re: Add id's to various elements in protocol.sgml - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Add id's to various elements in protocol.sgml
Date
Msg-id d65e170d-0017-5c9c-fff7-fc8f5fb042c6@enterprisedb.com
Whole thread Raw
In response to Re: Add id's to various elements in protocol.sgml  (Brar Piening <brar@gmx.de>)
Responses Re: Add id's to various elements in protocol.sgml  (Brar Piening <brar@gmx.de>)
List 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.




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PG DOCS - logical replication filtering
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Optionally automatically disable logical replication subscriptions on error