Skip to content

Commit 77d0ad6

Browse files
committed
Doc: suppress "exceed the available area" warning in PDF build.
Allow a line break in example output, as we have done elsewhere. Overlength output was added in commit 1e68e43. While here, adjust some shaky grammar in an adjacent note (from a different commit, c9af054). Per buildfarm.
1 parent 5e42827 commit 77d0ad6

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/src/sgml/monitoring.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1120,7 +1120,7 @@ SELECT a.pid, a.wait_event, w.description
11201120
pg_wait_events w ON (a.wait_event_type = w.type AND
11211121
a.wait_event = w.name)
11221122
WHERE wait_event is NOT NULL and a.state = 'active';
1123-
-[ RECORD 1 ]------------------------------------------------------------------
1123+
-[ RECORD 1 ]------------------------------------------------------&zwsp;------------
11241124
pid | 686674
11251125
wait_event | WALInitSync
11261126
description | Waiting for a newly initialized WAL file to reach durable storage
@@ -1130,11 +1130,11 @@ description | Waiting for a newly initialized WAL file to reach durable storage
11301130
<note>
11311131
<para>
11321132
Extensions can add <literal>Extension</literal> and
1133-
<literal>LWLock</literal> types
1134-
to the list shown in <xref linkend="wait-event-extension-table"/> and
1133+
<literal>LWLock</literal> events
1134+
to the lists shown in <xref linkend="wait-event-extension-table"/> and
11351135
<xref linkend="wait-event-lwlock-table"/>. In some cases, the name
1136-
of <literal>LWLock</literal> assigned by an extension will not be
1137-
available in all server processes; It might be reported as just
1136+
of an <literal>LWLock</literal> assigned by an extension will not be
1137+
available in all server processes. It might be reported as just
11381138
<quote><literal>extension</literal></quote> rather than the
11391139
extension-assigned name.
11401140
</para>

0 commit comments

Comments
 (0)