From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ansley, Michael <Michael.Ansley@intec.co.za>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] 8K query limit in 6.5?
Date: Tue, 13 Jul 1999 11:46:08 -0400
Message-ID: <23258.931880768@sss.pgh.pa.us> (raw)
In-Reply-To: <1BF7C7482189D211B03F00805F8527F70ED026@S-NATH-EXCH2>
"Ansley, Michael" <Michael.Ansley@intec.co.za> writes:
> Why are these limits even an issue? Surely I should be able to adjust
> certain constants in the code (and this would include constants to take care
> of the tuple length) in order to adjust the performance of the system. I
> realise that life is not that simple, but perhaps it could be made simpler
> than it is now. At the moment, some of the constants used are pretty
> useless, because they can't really be adjusted.
> Can't we come up with a way to make this more amenable to adjustment?
If it bothers you, step right up and fix it ...
Where I was actually hoping to end up is with no fixed limit at all,
ie make all buffers for text be dynamically resizable to handle the
longest query presented in a given session. But it'd be a useful
intermediate step to find all the places that are dependent on max query
length and drive them all from a single config.h constant. All that
code would eventually be replaced, if we do dynamic sizing, but doing
this would still be helpful as a way of identifying everything that
needs to change. Just finding all the places that depend on max query
length is not as trivial as you might think.
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-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, Michael.Ansley@intec.co.za
Subject: Re: [INTERFACES] 8K query limit in 6.5?
In-Reply-To: <23258.931880768@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