Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3XMz-0005fr-6e for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 20:47:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W3XMy-0003Fs-LI for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 20:47:24 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3XMx-0003F5-KX for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 20:47:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3XMv-0006cA-Gq for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 20:47:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s0FKlDla032426; Wed, 15 Jan 2014 15:47:13 -0500 From: Tom Lane To: Bruce Momjian cc: Pavel Stehule , pgsql-docs Subject: Re: remove undocumented assign syntax from plpgsql doc In-reply-to: <20140115203604.GA30822@momjian.us> References: <20140113025904.GB22464@momjian.us> <20140113140433.GA7868@momjian.us> <20140114202128.GA7761@momjian.us> <20140115153535.GA7607@momjian.us> <20140115163259.GA12704@momjian.us> <20140115203604.GA30822@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Wed, 15 Jan 2014 15:36:04 -0500" Date: Wed, 15 Jan 2014 15:47:13 -0500 Message-ID: <32425.1389818833@sss.pgh.pa.us> X-Pg-Spam-Score: -2.2 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Bruce Momjian writes: > On Wed, Jan 15, 2014 at 05:39:22PM +0100, Pavel Stehule wrote: > Uh, I see it in the documented syntax: > OPEN bound_cursorvar ( > argument_name := <--- > argument_value It is there, if you look into read_cursor_args(). This appears to be the only place in pl_gram.y where we don't treat '=' and COLON_EQUALS interchangeably. I was about to suggest that we should accept "=" here too, but on second thought that could break existing code, if anyone's using boolean equality expressions in cursor arguments. So we'd better accept the inconsistency. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs