From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: |
Date: | 2006-01-24 15:58:47 |
Message-ID: | 19199.1138118327@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rick Gigger <rick(at)alpinenetworking(dot)com> writes:
> Every once in a while I've noticed the number of processes I've got
> running jumps up a little higher than normal. So I check it out and
> realize that I'm building up a bunch of processes that just aren't
> completing. About half of the one's not completing say "SELECT
> waiting". I'm not doing anything that I am aware of that could be
> blocking anything. I am only doing regular vacuums. I am not
> explicitly locking anything that I know of. Is there a way to figure
> out what each of these processes are waiting on?
Look at the pg_locks view to see what locks they are waiting for and
who's got conflicting locks.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2006-01-24 16:02:19 | Re: Does this look ethical to you? |
Previous Message | Tom Lane | 2006-01-24 15:56:40 | Re: user defined function |