From: | "Mat Caughron" <caughron(at)gmail(dot)com> |
---|---|
To: | "Meredith L(dot) Patterson" <mlp(at)thesmartpolitenerd(dot)com>, sfpug(at)postgresql(dot)org |
Subject: | Re: IN question |
Date: | 2008-12-14 23:27:52 |
Message-ID: | d5aeb68a0812141527i43a61d47q283ca87275cacc15@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | sfpug |
Regarding query size:
In general, is there an approved way to get the parser to indicate
average length of query size?
Seems like this could have potential as a useful metric for tuning.
One could imagine a parser that varied allowable query size by how
many standard deviations it varies from what's normal. The thought
here being that anything too far out of the ordinary would require
human attention and custom tuning effort regardless of what else is
known about such a system.
Caveat: I've had to work on a lot of systems where clients (of the app
and/or database) can't be trusted, so the desirability of limited
query size seems very natural to me.
Mat Caughron
(408) 910-1266
On Sun, Dec 14, 2008 at 12:32 AM, Meredith L. Patterson
<mlp(at)thesmartpolitenerd(dot)com> wrote:
> A. Elein Mustain wrote:
>> I know about idiot clients and I am not one of them.
>> People writing extra large queries on "accident" are easily
>> culled.
>
> I'm pretty sure the idiot clients in question are the kind that don't
> generate code by typing it themselves, e.g. automated query builders.
>
>> I do complex warehouse type queries
>
> So, in your experience, what's an upper bound on the length of these
> queries?
>
> --mlp
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2008-12-15 18:24:50 | Re: IN question |
Previous Message | Meredith L. Patterson | 2008-12-14 08:32:28 | Re: IN question |