From: William P. <wil...@ya...> - 2010-03-21 16:04:24
|
Thanks for investigating this so quickly. I'm going to hazard a guess that the long time-out queries may be the result of robots clicking on anything clickable. If we don't have a robots.txt file in place, can we add a few in relevant places? bp On Mar 21, 2010, at 10:37 AM, Jon Auman wrote: > The database disk volume was thrown offline. This is not good. I had this happen before and I'm fairly certain that the application query issues is throwing the database into a deadlock. I've submitted a bug for this that has been deemed not critical, but I think that decision should be reconsidered. > > Meanwhile, I will look to see if postgresql has options to limit the time a query will run. Alternately, I will need to right a cron job that will kill the processes of hung queries. > > -Jon |