From: | Adam Bultman <adam(dot)bultman(at)iconideas(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Killing postgres processes. |
Date: | 2002-07-23 14:11:37 |
Message-ID: | 1027433527.17185.9.camel@twiki.iconideas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Greetings. I've got a postgres server that's being hit rather heavily.
I have many processes inititated by users (they start scripts running).
Because of user impatience and idiocy, despite my explanations, they
continue to re-run the script and not wait for the script to end the
first time (i.e. 'why isn't it finishing? <click click click>'). So, I
have about 9 postgres SELECTS going on right now that are pretty much
runaway and useless. Can I safely kill these without fubaring things?
I know killing the postmaster is Evil, but how about other processes?
i'm going to get a call in a few moments now in complaint, and I'd like
to be able to curb this right away.
Adam
--
Adam Bultman
adam(dot)bultman(at)iconideas(dot)com
616-836-7213
http://www.iconideas.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tuomas Vanhanen | 2002-07-23 14:35:24 | Security, IP and username restrictions |
Previous Message | Andrew McMillan | 2002-07-23 08:49:04 | Re: table move across databases |