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: Thu, 08 Feb 2007 17:29:23 -0500
Message-ID: <45CBA443.9090101@intellicon.biz> (raw)
In-Reply-To: <20601.1170972476@sss.pgh.pa.us>
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>
	<20601.1170972476@sss.pgh.pa.us>

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

The server is running on the same actual production data, schema and 
workload as before.

> Did you decide to start running autovacuum when you updated to 8.2?

Autovacuum was on and functioning before the update.

> How many tables are visible in the pg_stats views?

There are about 15 databases in the cluster each with around 90 tables. 
  A count of pg_stats yields between 500 and 800 rows in each database.

select count(*) from (select distinct tablename from pg_stats) as i;
  count
-------
     92
(1 row)

select count(*) from pg_stats;
  count
-------
    628
(1 row)

-- 
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: <45CBA443.9090101@intellicon.biz>
Permalink:  ../45CBA443.9090101@intellicon.biz/
Also on:    postgresql.org/message-id/45CBA443.9090101@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: <45CBA443.9090101@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