From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Olbersen <DOlbersen@stbernard.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Line length in pl/pgsql function
Date: Wed, 17 Mar 2004 00:35:47 -0500
Message-ID: <21150.1079501747@sss.pgh.pa.us> (raw)
In-Reply-To: <E7E213858379814A9AE48CA6754F5ECB0D749E@mail01.stbernard.com>
References: <E7E213858379814A9AE48CA6754F5ECB0D749E@mail01.stbernard.com>
"David Olbersen" <DOlbersen@stbernard.com> writes:
> I was minding my business, writing a nice long pl/pgsql function and all was well. I tried creating the function (using \i <file-with-definition>) and started getting funny errors.
> I figured out eventually that the problem seems due to line length in a construct of: FOR result IN <SELECT ...> LOOP
Hmm ... plpgsql had some string-length issues as recently as 7.2.2, but
I don't know of any problems since then. Could you submit a *complete*
test case, rather than making us guess the details?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, DOlbersen@stbernard.com
Subject: Re: Line length in pl/pgsql function
In-Reply-To: <21150.1079501747@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox