Docs: clarify description of LIMIT/OFFSET behavior.

Section 7.6 was a tad confusing because it specified what LIMIT NULL
does, but neglected to do the same for OFFSET NULL, making this look
like perhaps a special case or a wrong restatement of the bit about
LIMIT ALL.  Wordsmith a bit while at it.  Per bug #14084.

diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index b37adaa9ee6e53e7f34d17b788449d9db9d90c1c..718262f1aa7126a6ab3d67a4a0b9d702c17c2ac7 100644 (file)
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -1794,16 +1794,19 @@ SELECT select_list
 
   
    If a limit count is given, no more than that many rows will be
-   returned (but possibly less, if the query itself yields less rows).
+   returned (but possibly fewer, if the query itself yields fewer rows).
    LIMIT ALL is the same as omitting the LIMIT
-   clause.
+   clause, as is LIMIT with a NULL argument.
   
 
   
    OFFSET says to skip that many rows before beginning to
    return rows.  OFFSET 0 is the same as omitting the
-   OFFSET clause, and LIMIT NULL is the same
-   as omitting the LIMIT clause.  If both OFFSET
+   OFFSET clause, as is OFFSET with a NULL argument.
+  
+
+  
+   If both OFFSET
    and LIMIT appear, then OFFSET rows are
    skipped before starting to count the LIMIT rows that
    are returned.