From: Tom Lane <tgl@sss.pgh.pa.us>
To: Benjamin Minshall <minshall@intellicon.biz>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization
Date: Fri, 09 Feb 2007 11:33:06 -0500
Message-ID: <1116.1171038786@sss.pgh.pa.us> (raw)
In-Reply-To: <45CCA0DB.2010903@intellicon.biz>
References: <45CB5D06.7090004@intellicon.biz>
<7994.1170960391@sss.pgh.pa.us>
<45CB9330.3000603@intellicon.biz>
<19935.1170969862@sss.pgh.pa.us>
<45CB9C4D.30902@intellicon.biz>
<20601.1170972476@sss.pgh.pa.us>
<45CBA443.9090101@intellicon.biz>
<7959.1170986672@sss.pgh.pa.us>
<62089.75.14.32.120.1170994418.squirrel@intellicon.biz>
<14668.1170995218@sss.pgh.pa.us>
<20070209142459.GB4253@alvh.no-ip.org>
<24717.1171033699@sss.pgh.pa.us>
<29832.1171036557@sss.pgh.pa.us>
<45CCA0DB.2010903@intellicon.biz>
Benjamin Minshall <minshall@intellicon.biz> writes:
> When I checked on the server this morning, the huge stats file has
> returned to a normal size. I set up a script to track CPU usage and
> stats file size, and it appears to have decreased from 90MB down to
> about 2MB over roughly 6 hours last night. The CPU usage of the stats
> collector also decreased accordingly.
> The application logs indicate that there was no variation in the
> workload over this time period, however the file size started to
> decrease soon after the nightly pg_dump backups completed. Coincidence
> perhaps?
Well, that's pretty interesting. What are your vacuuming arrangements
for this installation? Could the drop in file size have coincided with
VACUUM operations? Because the ultimate backstop against bloated stats
files is pgstat_vacuum_tabstat(), which is run by VACUUM and arranges to
clean out any entries that shouldn't be there anymore.
It's sounding like what you had was just transient bloat, in which case
it might be useful to inquire whether anything out-of-the-ordinary had
been done to the database right before the excessive-CPU-usage problem
started.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, minshall@intellicon.biz, alvherre@commandprompt.com
Subject: Re: stats collector process high CPU utilization
In-Reply-To: <1116.1171038786@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox