From: | ken(dot)corey(at)atomic-interactive(dot)com |
---|---|
To: | "pos2" <pgsql-novice(at)postgresql(dot)org> |
Subject: | How do I tell? |
Date: | 2001-05-08 14:25:43 |
Message-ID: | 20010508142543.4885.qmail@atomic-interactive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi All,
I'm currently running postgres 7.1b3 (Yes, I know it's an older version),
and I'm seeing some strange behavior.
I've got a web browser and a jserv engine that start up 40 connections to
the database when they are started. When load on the database machine gets
high, I'll have 1 or 2 processes that won't ever end. They'll just
continue, soaking up CPU until I kill the database server.
My question isn't so much about the behavior itself (I'm presuming I've done
something bone-headed), but about the debugging of the behavior.
Is there any way in which I can see exactly the query that a postgres
process is processing? I know that with 'ps -auxww' I can see the state of
a given postgres process (idle/SELECT/SELECT waiting)...but how do I find
out that that SELECT really is:
"SELECT * from everything joined with everything else and a couple of outer
joins, order by, group by and limit"
--
Ken Corey CTO http://www.atomic-interactive.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-05-08 15:12:14 | Re: How do I tell? |
Previous Message | Hugh Williams | 2001-05-07 23:08:17 |