Thread: 8K query limit in 6.5?
Greetings, Was the 8K query limit increased in 6.5? Thanks, Matthew
Matthew Hagerty <matthew@venux.net> writes:
> Was the 8K query limit increased in 6.5?
Nope.
I tried to stir up some enthusiasm for fixing it in 6.6, but didn't
have much success --- too soon to say whether it will happen for 6.6
or be postponed again.
regards, tom lane
stir, stir, stir... please make this bigger! Or tell me how and I'll do it. :) Is it really such a big deal to increase the size of a query that pg can handle? I'm talking about the size of a query submitted to pg, from what I understand there is no limit on the record (tuple) size that can be returned from pg. Is my understanding correct? Thanks, Matthew At 09:59 AM 7/13/99 -0400, Tom Lane wrote: >Matthew Hagerty <matthew@venux.net> writes: >> Was the 8K query limit increased in 6.5? > >Nope. > >I tried to stir up some enthusiasm for fixing it in 6.6, but didn't >have much success --- too soon to say whether it will happen for 6.6 >or be postponed again. > > regards, tom lane >
Matthew Hagerty <matthew@venux.net> writes:
> ... please make this bigger! Or tell me how and I'll do it. :)
"Find all the places that need fixing, and fix 'em." :-)
The devil is in the details ... and there are a lot of details.
You could probably get some useful functionality just by fixing
frontend libpq's output buffer and the query input buffer in
backend/tcop/postgres.c. The trouble comes in cleaning up all the
details, like fixed-size buffers in COPY, pg_dump, etc etc etc etc.
Michael Ansley seems to be interested in working on this; I'd
suggest getting together with him if you want to help.
> Is it really such a big deal to increase the size of a query that pg can
> handle? I'm talking about the size of a query submitted to pg, from what I
> understand there is no limit on the record (tuple) size that can be
> returned from pg. Is my understanding correct?
There is a (quite unrelated) limit on the size of a tuple that can be
stored on disk, but AFAIK you can construct an arbitrarily large tuple
as the result of computations specified in a SELECT and it will be
passed back to your frontend application without trouble; as long as
you don't run out of memory on either side, that is.
Where we want to end up, of course, is no limit on the size of a disk
tuple either, but the code changes for that are almost entirely
unrelated to the ones that deal with the textual length of a query.
It's best tackled as two independent projects.
regards, tom lane
you can fix this by changing #define BLCKSZ 8192 in include/config.h On Mon, 12 Jul 1999, Matthew Hagerty wrote: > Greetings, > > Was the 8K query limit increased in 6.5? > > Thanks, > Matthew > ====================================================== Jeff MacDonaldjeff@hub.org webpage: http://hub.org/~jeffjeff@pgsql.com irc: bignose on EFnet ======================================================