pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Benjamin Minshall <minshall@intellicon.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization
Date: Thu, 08 Feb 2007 17:07:56 -0500
Message-ID: <20601.1170972476@sss.pgh.pa.us> (raw)
In-Reply-To: <45CB9C4D.30902@intellicon.biz>
References: <45CB5441.1040707@intellicon.biz>
	<21013.1170955076@sss.pgh.pa.us>
	<45CB5D06.7090004@intellicon.biz>
	<7994.1170960391@sss.pgh.pa.us>
	<45CB9330.3000603@intellicon.biz>
	<19935.1170969862@sss.pgh.pa.us>
	<45CB9C4D.30902@intellicon.biz>

Benjamin Minshall <minshall@intellicon.biz> writes:
> Seems the problem may be related to a huge global/pgstat.stat file. 
> Under 8.1.5 it was about 1 MB; now it's 90 MB in 8.2.3.

Yoi.  We didn't do anything that would bloat that file if it were
storing the same information as before.  What I'm betting is that it's
storing info on a whole lot more tables than before.  Did you decide
to start running autovacuum when you updated to 8.2?  How many tables
are visible in the pg_stats views?

			regards, tom lane



view thread (27+ messages)  latest in thread

Message-ID: <20601.1170972476@sss.pgh.pa.us>
Permalink:  ../20601.1170972476@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20601.1170972476@sss.pgh.pa.us

 · 

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