Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 245199FB692; Fri, 6 Apr 2007 22:55:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 34457-03; Fri, 6 Apr 2007 22:55:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.trinitydigital.com.au (unknown [202.134.38.99]) by postgresql.org (Postfix) with ESMTP id 5F8C29FB632; Fri, 6 Apr 2007 22:55:12 -0300 (ADT) Received: from [172.17.73.18] (C-59-101-233-61.bur.connect.net.au [59.101.233.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.trinitydigital.com.au (Postfix) with ESMTP id 4E7A5D6A; Sat, 7 Apr 2007 11:54:00 +1000 (EST) Message-ID: <4616F98B.9020506@pws.com.au> Date: Sat, 07 Apr 2007 11:53:15 +1000 From: Russell Smith User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Tom Lane CC: David Fetter , PostgreSQL Docs , PostgreSQL Patches Subject: Re: [DOCS] Fix misleading references to columns in GRANT/REVOKE summaries References: <20070406234603.GI3784@fetter.org> <29960.1175907960@sss.pgh.pa.us> In-Reply-To: <29960.1175907960@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/201 X-Sequence-Number: 1768 Tom Lane wrote: > David Fetter writes: > >> Per a question Alexey Parshin asked in the IRC channel, I'm attaching >> a patch to the GRANT and REVOKE syntax summaries which replaces the >> misleading word "column" with "parameter." "Column" is misleading >> because it could be read to imply a column-level GRANT/REVOKE, which >> we don't have yet. >> > > Apparently it's so misleading that you didn't understand it either. > The entire *point* of that paragraph is that we don't have the > feature. This proposed change is surely not an improvement... > Maybe removing the entire example would be more helpful. I don't find it clear to have a command outline in a compatibility block. > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > >