mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tweak wording in sequence-function docs to avoid PDF build failures.

Browse Source 
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.
This commit is contained in:
Tom Lane 2013-06-27 00:28:12 -04:00
parent d5ce39365f
commit 57a2155ebb
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/func.sgml
View File

@ -8786,12 +8786,11 @@ table2-mapping
</indexterm>
<para>
This section describes <productname>PostgreSQL</productname>'s
functions for operating on <firstterm>sequence objects</firstterm>.
Sequence objects (also called sequence generators or just
sequences) are special single-row tables created with <xref
This section describes functions for operating on <firstterm>sequence
objects</firstterm>, also called sequence generators or just sequences.
Sequence objects are special single-row tables created with <xref
linkend="sql-createsequence" endterm="sql-createsequence-title">.
A sequence object is usually used to generate unique identifiers
Sequence objects are commonly used to generate unique identifiers
for rows of a table. The sequence functions, listed in <xref
linkend="functions-sequence-table">, provide simple, multiuser-safe
methods for obtaining successive sequence values from sequence