I recently increased the default tuple size to 32K on Postgres 7.0.2
with no problems. My colleague, however, told me that I can't pass a
text string greater than 16 K into the PQexec C function. So his claim
is that the only way I can actually get > 16 K into the tuple is through
a binary cursor. Anyone know if this is correct? Is there some
configuration variable I can change to up this to the same size as the
maximum tuple length?

Thanks.
-Tony



Thu, 10 Aug 2000 10:01:44 -0700
"G. Anthony Reina" <reina@nsi.edu>
Input strings > 16 K?
"G. Anthony Reina" <reina@nsi.edu> writes:
> I recently increased the default tuple size to 32K on Postgres 7.0.2
> with no problems. My colleague, however, told me that I can't pass a
> text string greater than 16 K into the PQexec C function.

There *was* such a restriction in libpq, before 7.0.  His info is
obsolete...

			regards, tom lane

Fri, 11 Aug 2000 10:48:45 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: Input strings > 16 K? 
Tom Lane wrote:

> "G. Anthony Reina" <reina@nsi.edu> writes:
> > I recently increased the default tuple size to 32K on Postgres 7.0.2
> > with no problems. My colleague, however, told me that I can't pass a
> > text string greater than 16 K into the PQexec C function.
>
> There *was* such a restriction in libpq, before 7.0.  His info is
> obsolete...
>
>                         regards, tom lane

Thanks Tom. Good to know that the restriction was lifted.

-Tony




Fri, 11 Aug 2000 09:19:42 -0700
"G. Anthony Reina" <reina@nsi.edu>
Re: Input strings > 16 K?