From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Nik <XLPizza(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres using 100% CPU |
Date: | 2006-02-15 17:25:07 |
Message-ID: | b42b73150602150925o7cf398dbhdcda2ef61fa7c1c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
n 14 Feb 2006 06:46:48 -0800, Nik <XLPizza(at)gmail(dot)com> wrote:
> I turned off stats collector, and any row stat collectors, and I
> increased the number of check points since I have been getting the
> error about check point switches being to frequent. Postgres now uses a
> bit less CPU (60-90%), which is still a lot considering that no
> processing is being done. Is there anything else I can do to lower this
> CPU utilization? Is there a way I can pinpoint exactly what part of
> postgres is using this CPU?
something is seriously wrong. Fire up the task manager and determine
the pid of the process that is sucking cpu. Then query
pg_stat_activity to determine who/what is doing it (you will have to
restore stats). consider setting statement logging to get the exact
offender.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Duddridge | 2006-02-15 17:40:39 | Re: indexes for ILIKE |
Previous Message | Chad | 2006-02-15 17:05:26 | I see this as the end of BDB in MySQL without a doubt. |