[Babase] I killed 3 SELECT queries

Susan Alberts alberts at duke.edu
Sun Oct 17 13:54:29 EDT 2010


I think you should probably kill them. I am copying this to Beth to  
make sure - I don't know whether she is on the listserv (will be soon  
if not already).

Questions this raises:
-can we make it so that a person can kill their own jobs? I always ask  
Lacey to when I get out of control, but it would useful if I could do  
it directly. Or can I and I just don't know it?

-Jeanne and Niki and Lacey and I need to come up with some sort of  
tutorial and/or registration for users that are new so that we know  
they know how to let us know when things need to be killed etc. Lacey,  
let's put that on the next babase conf call.

Susan

On Oct 17, 2010, at 12:29 AM, Karl O. Pinc wrote:

> On 10/16/2010 10:35:38 PM, Karl O. Pinc wrote:
>> Hi,
>>
>> FYI.  I just killed 3 SELECT queries run by
>> postgres user 'archie' that had been running
>> for more than 860 CPU minutes (13 hours) each.
>>
>> Now there seems to be another that's started....
>
> That one's been running for most of a cpu hour.
>
> I killed it and the one that started after it as
> well.  That seemed to have exhausted what's
> been queued up.
>
> Please let me know if this is all a bad idea
> and I should leave such jobs running.
>
> Thanks.
>
>
>
> Karl <kop at meme.com>
> Free Software:  "You don't pay back, you pay forward."
>                 -- Robert A. Heinlein
>
>
> _______________________________________________
> Babase mailing list
> Babase at www.eco.princeton.edu
> http://www.eco.princeton.edu/mailman/listinfo/babase

------------------------------------------------------------
Susan Alberts, Professor of Biology, Duke University, Box 90338,  
Durham NC 27708. Phone 919-660-7272, FAX 919-660-7293






More information about the Babase mailing list