func.sgml - Mailing list pgsql-hackers

From Andrew Dunstan
Subject func.sgml
Date
Msg-id 53fdd499-bb38-6cb0-5792-cce3709ef47d@dunslane.net
Whole thread Raw
Responses Re: func.sgml  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: func.sgml  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
Re: func.sgml  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-hackers
At
<https://www.postgresql.org/message-id/543620.1629899413%40sss.pgh.pa.us>
Tom noted:

> You have to be very careful these days when applying stale patches to
> func.sgml --- there's enough duplicate boilerplate that "patch' can easily
> be fooled into dumping an addition into the wrong place. 

This is yet another indication to me that there's probably a good case
for breaking func.sgml up into sections. It is by a very large margin
the biggest file in our document sources (the next largest is less than
half the number of lines).


thoughts?


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [PATCH] Don't block HOT update by BRIN index
Next
From: Tom Lane
Date:
Subject: Re: func.sgml