Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id E01541337B47 for ; Sat, 2 Apr 2011 13:53:29 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 45657-08 for ; Sat, 2 Apr 2011 16:53:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 087581337B43 for ; Sat, 2 Apr 2011 13:53:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p32Gr8QX026890; Sat, 2 Apr 2011 12:53:08 -0400 (EDT) To: Alvaro Herrera cc: Pg Docs Subject: Re: psql's \h MOVE In-reply-to: <1301670352-sup-4920@alvh.no-ip.org> References: <1301670352-sup-4920@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Fri, 01 Apr 2011 12:17:18 -0300" Date: Sat, 02 Apr 2011 12:53:08 -0400 Message-ID: <26889.1301763188@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201104/7 X-Sequence-Number: 6578 Alvaro Herrera writes: > I just noticed that \h MOVE is particularly unhelpful: > alvherre=# \h move > Command: MOVE > Description: position a cursor > Syntax: > MOVE [ direction { FROM | IN } ] cursorname > The problem is that it doesn't specify what "direction" is. The doc > text tells you to look into FETCH for details, but in \h you have to > guess. > We could fix this by including a note about fetch in the , > so that it'd look like this: > alvherre=# \h move > Command: MOVE > Description: position a cursor > Syntax: > MOVE [ direction [ FROM | IN ] ] cursor_name > See FETCH for details on direction -1 ... if this annoys you, just duplicate the definition of direction from FETCH. regards, tom lane