On Sat, Aug 05, 2006 at 03:12:48PM -0700, Aaron Stone wrote:
> On Sat, 2006-08-05 at 02:13 -0400, Leif Jackson wrote:
> > We could make the query string dynamicly size it self with a realloc or
> > somthing to that effect, then the question just would be would that open
> > up a DDoS of some sort... But just for the utils and such that might come
> > accross a query larger than the default it might solve and issue such as
> > this one?
>
> We saw a few queries in the past that could be truncated and just tuned
> down the inputs to those queries. That's the easiest way to handle
> single situations, but we should think about a better solution for the
> future. The query interface based around prepared statements that's been
> discussed on the list before would be the right place to put a bit more
> intelligence about query length. I tossed a note on the wiki about it.
Speaking from a PostgreSQL perspective, for some cases the best bet will
be to...
CREATE TEMP TABLE blah (
id int8 NOT NULL
);
COPY blah FROM STDIN;
-- stream values in, one per line
\.
-- Run query that needs IDs, joining against blah.
BTW, is there some trick to getting an account on the bug tracker? I
keep trying to register, but the emails never make it to me.
--
Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
