Undocumented count in FORWARD/BACKWARD direction of MOVE statement - Mailing list pgsql-docs

From PG Doc comments form
Subject Undocumented count in FORWARD/BACKWARD direction of MOVE statement
Date
Msg-id 172155553388.702.7932496598218792085@wrigleys.postgresql.org
Whole thread Raw
Responses Re: Undocumented count in FORWARD/BACKWARD direction of MOVE statement
List pgsql-docs
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/16/plpgsql-cursors.html
Description:

The documentation shows this example for the MOVE statement:

MOVE FORWARD 2 FROM curs4;

According to the docs, this should not work. The count is documented only
for the directions ABSOLUTE and RELATIVE (which should be enough). "FORWARD
count" and "BACKWARD" count works in MOVE but not in FETCH. I don't know if
this is intentional. However, the docs do not seem to be correct for MOVE
directions.

pgsql-docs by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Fix an incorrect statement for failover option in alter_subscription.sgml
Next
From: shveta malik
Date:
Subject: Re: Fix an incorrect statement for failover option in alter_subscription.sgml