Skip to content

Commit 60d7edb

Browse files
committed
Tweak wording in sequence-function docs to avoid PDF build failures.
Adjust the wording in the first para of "Sequence Manipulation Functions" so that neither of the link phrases in it break across line boundaries, in either A4- or US-page-size PDF output. This fixes a reported build failure for the 9.3beta2 A4 PDF docs, and future-proofs this particular para against causing similar problems in future. (Perhaps somebody will fix this issue in the SGML/TeX documentation tool chain someday, but I'm not holding my breath.) Back-patch to all supported branches, since the same problem could rise up to bite us in future updates if anyone changes anything earlier than this in func.sgml.
1 parent 1f3fbce commit 60d7edb

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

doc/src/sgml/func.sgml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9702,12 +9702,11 @@ table2-mapping
97029702
</indexterm>
97039703

97049704
<para>
9705-
This section describes <productname>PostgreSQL</productname>'s
9706-
functions for operating on <firstterm>sequence objects</firstterm>.
9707-
Sequence objects (also called sequence generators or just
9708-
sequences) are special single-row tables created with <xref
9705+
This section describes functions for operating on <firstterm>sequence
9706+
objects</firstterm>, also called sequence generators or just sequences.
9707+
Sequence objects are special single-row tables created with <xref
97099708
linkend="sql-createsequence">.
9710-
A sequence object is usually used to generate unique identifiers
9709+
Sequence objects are commonly used to generate unique identifiers
97119710
for rows of a table. The sequence functions, listed in <xref
97129711
linkend="functions-sequence-table">, provide simple, multiuser-safe
97139712
methods for obtaining successive sequence values from sequence

0 commit comments

Comments
 (0)