From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ralph Graulich <maillist(at)shauny(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: size of function body |
Date: | 2002-07-16 21:22:40 |
Message-ID: | 4887.1026854560@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ralph Graulich <maillist(at)shauny(dot)de> writes:
> Given a function with 29 parameters, consisting of 5 INTEGERs and the rest
> being VARCHARs, reALIASing all the parameter in the DECLARE block and
> using them in several SQL statements within the function's body, I began
> to receive that error:
> ERROR: parser: parse error at or near "SELECT" 89299<
Hmm. Are there any long literal strings in your function text? (Not
sure, but I think "long" may mean "> 256 bytes" in this context.) If
so, you might be running into a recently-discovered bug in plpgsql.
Try substituting the latest version of pl_funcs.c, see
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_funcs.c
If that doesn't do it for you, we'll need to see a reproducible test
case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-16 21:31:05 | Re: Question: merit / feasibility of compressing frontend |
Previous Message | Andrew Sullivan | 2002-07-16 20:53:05 | Re: table size growing out of control |