| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: fix examples for pg_input_error_info(). |
| Date: | 2023-03-24 23:31:32 |
| Message-ID: | E1pfqsd-005ESu-Vu@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Doc: fix examples for pg_input_error_info().
These were causing "contents ... exceed the available area"
warnings in PDF builds, and also didn't quite follow our markup
conventions for function examples. To fix the overwidth
problem, reduce the number of fields shown in one example,
and also insert &zwsp; to let the header line be broken in
a reasonable place.
Discussion: https://postgr.es/m/20230324194701.dqkzcdtlcikseo22@awork3.anarazel.de
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/7023207cfdb6d5863bdcc9c29bff9918846dddc6
Modified Files
--------------
doc/src/sgml/func.sgml | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-25 17:23:07 | pgsql: Doc: fix another "contents...exceed the available area" PDF warn |
| Previous Message | Andres Freund | 2023-03-24 21:22:40 | pgsql: docs: Explain how to silence overly verbose messages by fop |