Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 2FCD81337BE4
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sun,  3 Apr 2011 21:37:58 -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 69092-08 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Mon,  4 Apr 2011 00:37:40 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-px0-f174.google.com (mail-px0-f174.google.com
	[209.85.212.174])
	by mail.postgresql.org (Postfix) with ESMTP id 15F5713364DE
	for <pgsql-docs@postgresql.org>; Sun,  3 Apr 2011 21:37:39 -0300 (ADT)
Received: by pxi15 with SMTP id 15so1655378pxi.33
	for <pgsql-docs@postgresql.org>; Sun, 03 Apr 2011 17:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=yGqUZAPMX01bbBu63IUv+524pI2hAk3tcF/G8Pf3irk=;
	b=YaLmh6SX2yZlh3k032T6TJNxoSdPgkI5cVwTyi/q8KvYBQwF6YE3T5F6b8+vls1162
	zYzYaL0DESG852uhJXtEFyTK3PLEYXvTZy7IeKl5SqqQxzS6wdiy3bBlQQoK/O/4/Dsn
	WVtN+ptzlD14FTVdKQHd0ohC0bJOpwSFOyt4U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=hho4BwpkUDmn9EwmZnqe3h38YA+KtstL6jtMr06+cqqExXkGzD1zjtvhfcCiH8X0bv
	VeDjKnj2NTJPTKPLM0PJYrSAhVBbuYTPJFYSrRnD37awB5up0aaTWIRx0N1pUtSLI4lQ
	aGMJenoWvQIZlEbOf4X2ErRuAy/Jx2jEG+k98=
MIME-Version: 1.0
Received: by 10.142.60.5 with SMTP id i5mr6157038wfa.135.1301877459759; Sun,
	03 Apr 2011 17:37:39 -0700 (PDT)
Received: by 10.68.62.65 with HTTP; Sun, 3 Apr 2011 17:37:39 -0700 (PDT)
In-Reply-To: <26889.1301763188@sss.pgh.pa.us>
References: <1301670352-sup-4920@alvh.no-ip.org>
	<26889.1301763188@sss.pgh.pa.us>
Date: Sun, 3 Apr 2011 20:37:39 -0400
Message-ID: <BANLkTi=i=OFvkj0t_JK+0qvFwMi5db5_Jw@mail.gmail.com>
Subject: Re: psql's \h MOVE
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Pg Docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.899 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001
X-Spam-Level: 
X-Archive-Number: 201104/9
X-Sequence-Number: 6580

On Sat, Apr 2, 2011 at 12:53 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>> I just noticed that \h MOVE is particularly unhelpful:
>> =A0 =A0 =A0 alvherre=3D# \h move
>> =A0 =A0 =A0 Command: =A0 =A0 MOVE
>> =A0 =A0 =A0 Description: position a cursor
>> =A0 =A0 =A0 Syntax:
>> =A0 =A0 =A0 MOVE [ direction { FROM | IN } ] cursorname
>
>> The problem is that it doesn't specify what "direction" is. =A0The 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 <synopsis>,
>> so that it'd look like this:
>
>> =A0 =A0 =A0 alvherre=3D# \h move
>> =A0 =A0 =A0 Command: =A0 =A0 MOVE
>> =A0 =A0 =A0 Description: position a cursor
>> =A0 =A0 =A0 Syntax:
>> =A0 =A0 =A0 MOVE [ direction [ FROM | IN ] ] cursor_name
>
>> =A0 =A0 =A0 See FETCH for details on direction
>
> -1 ... if this annoys you, just duplicate the definition of direction
> from FETCH.

+1 for duplicating the definition.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company