Re: [Solved] 8.3 Stats Collector Stuck at 100% CPU

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: [Solved] 8.3 Stats Collector Stuck at 100% CPU
Date: 2010-04-01 14:45:08
Message-ID: 15963.1270133108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> The solution for me was simply to run pg_stat_reset(), and the problem
> went away within a few seconds. The $PGDATA/global/pgstat.stat file
> was 1.2GB before the reset, and went down to ~250KB after the reset.
> It looks like this file is adding on 4MB or so per day at the current
> rate, so I'll likely have to do this again in a few months.

Hm. It sounds like you are "leaking" stats collector table entries for
some reason. It would be good to fix the underlying problem rather than
just resign yourself to a manual workaround. Is there anything unusual
about your workload that might trigger this?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ozz Nixon 2010-04-01 15:05:21 Anyone using RubyRep replication?
Previous Message Alvaro Herrera 2010-04-01 13:58:33 Re: simultaneously reducing both memory usage and runtime for a query