On Tuesday 20 March 2001 07:58, Richard Ellerbrock wrote:
> It would also be VERY cool to be able to adjust the priority of selects
like you can with inserts. In some cases I know selects are going to take
long and thus do not want them to take all resources.
>
> Also, it would be REALLY cool to be able to specify a time limit for a
select after which time it would die. I know this can be set globally, but
this will not work for me as my server has many web apps (php driven) all
using the same database - each app having different requirements. What grinds
me is that some users enter crap searches on my apps and then hit the
stop/cancel button when it takes too long. I know in upcoming versions of php
they plan to somehow "fix" this - how I do not know. Oh yes, my
> databases are normalised.
For now the workaround would be to write a daemon or a cron job that connects
to MySQL once in a while, runs show full processlist, check the execution
time and command type, and kills all threads that have exceeded the limit on
select.
--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA
<___/
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
