| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | func.sgml |
| Date: | 2021-10-04 14:33:36 |
| Message-ID: | 53fdd499-bb38-6cb0-5792-cce3709ef47d@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-10-04 14:52:13 | Re: func.sgml |
| Previous Message | Tomas Vondra | 2021-10-04 14:17:47 | Re: [PATCH] Don't block HOT update by BRIN index |