diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 5b2aac618e..d6688e13f4 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3196,6 +3196,10 @@ FETCH direction { FROM | IN }
BACKWARD.
Omitting direction is the same
as specifying NEXT.
+ In the forms using a count,
+ the count can be any integer-valued
+ expression (unlike the SQL FETCH command,
+ which only allows an integer constant).
direction values that require moving
backward are likely to fail unless the cursor was declared or opened
with the SCROLL option.
@@ -3233,26 +3237,6 @@ MOVE direction { FROM | IN } <
be checked to see whether there was a next row to move to.
-
- The direction clause can be any of the
- variants allowed in the SQL
- command, namely
- NEXT,
- PRIOR,
- FIRST,
- LAST,
- ABSOLUTE count,
- RELATIVE count,
- ALL,
- FORWARD count | ALL , or
- BACKWARD count | ALL .
- Omitting direction is the same
- as specifying NEXT.
- direction values that require moving
- backward are likely to fail unless the cursor was declared or opened
- with the SCROLL option.
-
-
Examples:
diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml
index 5ef63f0058..e802be61c8 100644
--- a/doc/src/sgml/ref/fetch.sgml
+++ b/doc/src/sgml/ref/fetch.sgml
@@ -99,7 +99,7 @@ FETCH [ direction [ FROM | IN ] ] <
This page describes usage of cursors at the SQL command level.
If you are trying to use cursors inside a PL/pgSQL
function, the rules are different —
- see .
+ see .