So how can we terminate such a long running query ? The idea is to make a crontab to periodicaly do a job to search a typical "SELECT * FROM bigtable" query who has run for some hours then to terminate them... On 2/9/06, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: > > Is there a way to limit user's CPU resource specially on "SELECT" query ? > > > > I hava a table with a lot of rows inside, if one sloopy DB users do a > > "SELECT * FROM bigtable" > > then CPU resource will go near 99% and this action will surely affect > > the other database performance ... > > > Yes, the answer is not to write the query in the first place :-). you > can implement cursors, do client side browsing, or other techiniques > to handle this problem more elegantly. > > try to follow rule of thumb to return minimal amount of data necessary > to the client. > > Merlin >
