Re: [Solved] 8.3 Stats Collector Stuck at 100% CPU - Mailing list pgsql-general

From Tom Lane
Subject Re: [Solved] 8.3 Stats Collector Stuck at 100% CPU
Date
Msg-id 15963.1270133108@sss.pgh.pa.us
Whole thread Raw
In response to [Solved] 8.3 Stats Collector Stuck at 100% CPU  (Josh Kupershmidt <schmiddy@gmail.com>)
Responses Re: [Solved] 8.3 Stats Collector Stuck at 100% CPU  (Josh Kupershmidt <schmiddy@gmail.com>)
List pgsql-general
Josh Kupershmidt <schmiddy@gmail.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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: simultaneously reducing both memory usage and runtime for a query
Next
From: Alban Hertroys
Date:
Subject: Re: transaction control in pl/pgsql