Horton

Re: split func.sgml to separated individual sgml files

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>, Nazir Bilal Yavuz <byavuz81@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Florents Tselai <florents.tselai@gmail.com>, Euler Taveira <euler@eulerto.com>, jian he <jian.universality@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, Corey Huinker <corey.huinker@gmail.com>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-10-06T14:55:53Z
Lists: pgsql-hackers 
On Fri, Oct  3, 2025 at 10:41:56AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter@eisentraut.org> writes:
> > If you look at this more closely, creating postgres-full.xml and running 
> > the syntax check perform the same operations, except that the latter 
> > throws away the output.  So it seems redundant to build a whole new code 
> > path for this.  I think you can make the check target dependent on 
> > postgres-full.xml and be done, kind of like this (starting from 
> > pre-b2922562726):
> 
> Would it be unreasonable to discard the "check" target altogether?
> It made sense back in the day when actually building the html docs
> took many minutes.  But I haven't used it in years, so I wonder
> if anyone else has either.

I run 'make check' on the SGML every time I build the C code.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

Commits

  1. Revert "Improve docs syntax checking"

  2. Improve docs syntax checking

  3. Teach doc/src/sgml/Makefile about the new func/*.sgml files.

  4. Split func.sgml into more manageable pieces

  5. Doc: add check to detect non-breaking spaces in the docs.