From: | David Noel <david(dot)i(dot)noel(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, "freebsd-database(at)freebsd(dot)org" <freebsd-database(at)freebsd(dot)org> |
Subject: | Re: PostgreSQL: CPU utilization creeping to 100% |
Date: | 2013-04-02 23:08:36 |
Message-ID: | CAHAXwYAZaXBCJB_5=DvK2+tgPfQZj5YMPoUU_o570baivutMnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/2/13, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> David Noel <david(dot)i(dot)noel(at)gmail(dot)com> wrote:
>
>> 'select * from pg_stat_activity' shows that the queries are not
>> waiting, and are in the idle state.
>
> The process is idle or the process is running the query? If the
> latter, what do you mean when you say "the queries ... are in the
> idle state"?
select * from pg_stat_activity returns a table containing a column
labeled "state". When the postgres process is at 100% utilization and
the application has hung, this query returns the value "idle" in that
field. When things are running properly, as they are for the moment
now, the value is "active".
From | Date | Subject | |
---|---|---|---|
Next Message | David Noel | 2013-04-02 23:15:54 | Re: PostgreSQL: CPU utilization creeping to 100% |
Previous Message | David Noel | 2013-04-02 23:03:52 | Re: PostgreSQL: CPU utilization creeping to 100% |