| From: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
|---|---|
| To: | Erik Jones <erik(at)myemma(dot)com> |
| Cc: | Stefan Sturm <stefan(dot)s(dot)sturm(at)googlemail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Processes on a linux box |
| Date: | 2008-04-12 16:22:31 |
| Message-ID: | 20080412162231.GA20583@cns.vt.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 11, 2008 at 04:48:03PM -0500, Erik Jones wrote:
> On Apr 11, 2008, at 4:23 PM, Stefan Sturm wrote:
>> 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.
This is priceless:
http://www.postgresql.org/docs/8.3/static/explicit-locking.html
it explains the lock modes.
As for the data collection:
http://archives.postgresql.org/pgsql-general/2006-10/msg00841.php
this is the best starting place I've been able to find, hopefully
there is more and I've not found it.
Now what we need is some wise elaboration here:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-12 16:39:38 | Re: SQL injection, php and queueing multiple statement |
| Previous Message | Ivan Sergio Borgonovo | 2008-04-12 16:20:36 | Re: SQL injection, php and queueing multiple statement |