Re: BUG #14258: Documentation pl/pgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Дилян Палаузов <dpa-postgres(at)aegee(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14258: Documentation pl/pgsql
Date: 2016-07-21 22:17:55
Message-ID: 16087.1469139475@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> I'm hoping there is some kind of warning output during the PDF build
> process that can help locate these kinds of problems.

Yeah, look for "Overfull \hbox" in the TeX log. Unfortunately, the
warnings reference line numbers in TeX's input (the tex-pdf file,
which isn't even saved after the make is done :-(). So it's a pain
to work backwards to where the problem is in the SGML docs. But you
can if you're determined.

By my count, there are 3021 such warnings generated in current HEAD docs.
A lot of them are small enough to be negligible, but a lot are not.
There's about 450 that are for more than 72 points (an inch) of overflow.

I do not see a lot of value in attacking such problems one instance at a
time.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-07-21 22:25:13 Re: BUG #14258: Documentation pl/pgsql
Previous Message David G. Johnston 2016-07-21 21:53:39 Re: BUG #14258: Documentation pl/pgsql