| From: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com> |
|---|---|
| To: | "Vitaly Belman" <vitalyb(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Killing a session |
| Date: | 2004-08-21 20:45:24 |
| Message-ID: | 71E37EF6B7DCC1499CEA0316A256832801057E6F@loki.wc.globexplorer.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
kill -15 pid#
will kill a given thread ... you can look in the pg_stat_activity; the query_start shows when it started, the current_query shows at least a portion of the SQL the thread is executing, and procpid if the pid of the process to kill with a -15 command.
Not sure about Windows variants, though.
HTH
Greg Williamson
DBA
GlobeXplorer LLC
-----Original Message-----
From: Vitaly Belman [mailto:vitalyb(at)gmail(dot)com]
Sent: Sat 8/21/2004 1:32 PM
To: pgsql-general(at)postgresql(dot)org
Cc:
Subject: [GENERAL] Killing a session
Is there a way to kill a session in PostrgeSQL? I ran a bad query by
mistake and I don't want to shut the whole database just to quit using
the whole CPU.
--
ICQ: 1912453
AIM: VitalyB1984
MSN: tmdagent(at)hotmail(dot)com
Yahoo!: VitalyBe
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-22 00:14:53 | Re: Killing a session |
| Previous Message | Vitaly Belman | 2004-08-21 20:32:45 | Killing a session |