Horton

Re: Remaining PDF layout issues

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-docs@lists.postgresql.org
Date: 2020-05-12T05:10:06Z
Lists: pgsql-docs

Attachments

I wrote:
>> Table 27.4 is annoying: it could be made to work, just barely, with some
>> hacking of the column widths and a &zwsp; or two.  But it's not stable
>> text so I have little faith in the longevity of such a solution,
>> especially if people keep on inventing long wait event names.  I also
>> find it not very readable, even in a wide window.  The first idea that
>> comes to mind is to split it into multiple tables, one per "Wait Event
>> Type", so that we don't need the lefthand column.

Here's an attempt at doing it that way.  I think this might be a better
answer, although it's still subject to problems if anyone's logorrhea gets
any worse in naming wait conditions: "SerializablePredicateLockListLock"
is still going to force manually tweaking the column widths.

I sorted the names here, too.

			regards, tom lane

Commits

  1. Doc: hack on table 26.1 till it fits in PDF format.

  2. Doc: tweak examples to silence line-too-long PDF build warnings.

  3. Doc: split up wait_event table.

  4. Doc: hack table 13.2 "Conflicting Lock Modes" till it fits in PDF.

  5. Doc: fix remaining over-length entries in SQL keywords table.