Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fATNK1m36586 for ; Thu, 29 Nov 2001 18:20:01 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fATND5k03777; Thu, 29 Nov 2001 18:13:05 -0500 (EST) To: Stephan Szabo cc: =?us-ascii?Q?=22Johnny_J=F8rgensen=22?= , pgsql-sql@postgresql.org Subject: Re: PL/pgSQL loops? In-reply-to: <19090.1007053375@sss.pgh.pa.us> References: <20011129073009.E43179-100000@megazone23.bigpanda.com> <19090.1007053375@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Thu, 29 Nov 2001 12:02:55 -0500" Date: Thu, 29 Nov 2001 18:13:05 -0500 Message-ID: <3774.1007075585@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/423 X-Sequence-Number: 5805 I said: > I would've expected it to count nested parentheses, at least. Okay, it does that now, and I found that I could tighten the error checking to give a sooner/more useful error. Now, if you get caught by the integer-FOR-vs-FOR-over-rows problem, you'll probably get ERROR: missing .. at end of SQL expression which at least gives you some clue that the problem has something to do with the "FOR x IN foo .. bar" syntax. regards, tom lane