From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Stefan Sturm <stefan(dot)s(dot)sturm(at)googlemail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Processes on a linux box |
Date: | 2008-04-11 21:48:03 |
Message-ID: | F2D1B44F-8D74-49C5-B371-3DD1C486725F@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Apr 11, 2008, at 4:23 PM, Stefan Sturm wrote:
> Hello,
>
> Am 11.04.2008 um 18:41 schrieb Andrew Sullivan:
>
>> On Fri, Apr 11, 2008 at 03:09:43PM +0200, Stefan Sturm wrote:
>>> DBVisualizer stoped working and no I have two processes on my
>>> server:
>>> postgres 30873 0.0 0.7 46552 7124 ? Ss 12:33 0:01
>>> postgres: postgres dbName 10.0.1.198(53658) ALTER TABLE waiting
>>> postgres 31007 0.0 0.6 46708 6500 ? Ss 13:07 0:00
>>> postgres: postgres dbName 10.0.1.198(53799) SELECT waiting
>>>
>>> What can I do? OK, I can stop and start the Database, but I think
>>> there are other ways to handle this...
>>> What Tool can I use to kill such processes?
>>
>> Why do you want to kill them? They're waiting for a lock. What is
>> it?
>
> I don''t want to kill them. So how can I find out, what ist locking
> them?
> Is there a tool, which shows me such Information?
There is a system catalog view called pg_locks that has an attribute
called pid that you can use to search for entries for those procs.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bharat Patel | 2008-04-11 22:57:54 | Deleting row in 7.4 takes for ever |
Previous Message | Ivan Sergio Borgonovo | 2008-04-11 21:31:44 | Re: SQL injection, php and queueing multiple statement |