pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Benjamin Minshall <minshall@intellicon.biz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization
Date: Fri, 09 Feb 2007 13:36:03 -0500
Message-ID: <45CCBF13.2000707@intellicon.biz> (raw)
In-Reply-To: <1116.1171038786@sss.pgh.pa.us>
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>
	<1116.1171038786@sss.pgh.pa.us>

Tom Lane wrote:
> 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.

VACUUM and ANALYZE are done by autovacuum only, no cron jobs. 
autovacuum_naptime is 30 seconds so it should make it to each database 
every 10 minutes or so.  Do you think that more aggressive vacuuming 
would prevent future swelling of the stats file?

> 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.

I don't believe that there was any unusual activity on the server, but I 
have set up some more detailed logging to hopefully identify a pattern 
if the problem resurfaces.

Thanks.

-- 
Benjamin Minshall <minshall@intellicon.biz>
Senior Developer -- Intellicon, Inc.
http://www.intellicon.biz

Attachments:

  smime.p7s (application/x-pkcs7-signature, 5.1K) download

view thread (27+ messages)  latest in thread

Message-ID: <45CCBF13.2000707@intellicon.biz>
Permalink:  ../45CCBF13.2000707@intellicon.biz/
Also on:    postgresql.org/message-id/45CCBF13.2000707@intellicon.biz

 · 

reply
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: minshall@intellicon.biz, tgl@sss.pgh.pa.us
  Subject: Re: stats collector process high CPU utilization
  In-Reply-To: <45CCBF13.2000707@intellicon.biz>

* 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