Re: input buffer overflow, can't enlarge buffer because scanner uses REJECT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Murphy <murphy2(at)speakeasy(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: input buffer overflow, can't enlarge buffer because scanner uses REJECT
Date: 2003-05-05 01:07:29
Message-ID: 16522.1052096849@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kevin Murphy <murphy2(at)speakeasy(dot)net> writes:
> I'm using PG 7.2.3 , and a PL/pgSQL script is failing while trying to insert a
> very long constant string into a column of type 'text'. Actually, the PG
> backend just closes the connection to the client. The error message, which
> is given in the server log, is "input buffer overflow, can't enlarge buffer
> because scanner uses REJECT". I looked in the .conf file but didn't see
> anything like a configurable input buffer size.

> Any clues as to how to get around this?

How long is "very long"?

One way around it would be to pass the constant as a parameter instead
of embedding it into the plpgsql function's text.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message shoaib 2003-05-05 02:56:01 Database server restarting
Previous Message Kevin Murphy 2003-05-05 00:32:33 input buffer overflow, can't enlarge buffer because scanner uses REJECT