X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9795BD1DF4D for ; Wed, 17 Mar 2004 05:35:49 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 72181-03 for ; Wed, 17 Mar 2004 01:35:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 869E3D1E94E for ; Wed, 17 Mar 2004 01:35:47 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2H5ZlKH021151; Wed, 17 Mar 2004 00:35:47 -0500 (EST) To: "David Olbersen" Cc: pgsql-sql@postgresql.org Subject: Re: Line length in pl/pgsql function In-reply-to: References: Comments: In-reply-to "David Olbersen" message dated "Tue, 16 Mar 2004 16:47:34 -0800" Date: Wed, 17 Mar 2004 00:35:47 -0500 Message-ID: <21150.1079501747@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/183 X-Sequence-Number: 17282 "David Olbersen" writes: > I was minding my business, writing a nice long pl/pgsql function and all was well. I tried creating the function (using \i ) and started getting funny errors. > I figured out eventually that the problem seems due to line length in a construct of: FOR result IN