From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marcin Krol <mrkafk(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: viewing currently executing query |
Date: | 2008-11-05 15:42:10 |
Message-ID: | 14634.1225899730@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Marcin Krol <mrkafk(at)gmail(dot)com> writes:
> I use an app (developed by someone else) that uses Postgres 8.3 as
> backend. The app in question starts up for a rather long time, about 10
> minutes, during which Postgres is heavily loaded (several processes each
> eating 50%-100% of CPU on the multicore server).
> However, when I do "select * from pg_stat_activity" during the startup,
> all the connections seem to be idle (see below).
You seem to have missed the load --- most of those connections have been
idle for a minute or two.
> I have found here info that current query stats have to be explicitly
> turned on in postgresql.conf - is that true?
As of 8.3 they're on by default, see track_activities.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Hollingsworth | 2008-11-05 17:34:33 | basic security |
Previous Message | Tom Lane | 2008-11-05 15:28:12 | Re: Does pg_dumpall support BLOBs? |