From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: Chris <lists@deksai.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector suddenly causing lots of IO
Date: Fri, 16 Apr 2010 11:23:52 -0400
Message-ID: <9738.1271431432@sss.pgh.pa.us> (raw)
In-Reply-To: <z2s4ec1cf761004160739w3ac5511jd39263dd043e2da6@mail.gmail.com>
References: <20100413170105.GA29571@chris-laptop.a2hosting.com>
<25952.1271370711@sss.pgh.pa.us>
<z2s4ec1cf761004160739w3ac5511jd39263dd043e2da6@mail.gmail.com>
Josh Kupershmidt <schmiddy@gmail.com> writes:
> I'm not sure whether this is related to the stats collector problems
> on this machine, but I noticed alarming table bloat in the catalog
> tables pg_attribute, pg_attrdef, pg_depend, and pg_type.
Hmm. That makes me wonder if autovacuum is functioning properly at all.
What does pg_stat_all_tables show for the last vacuum and analyze times
of those tables? Try something like
select relname,n_live_tup,n_dead_tup,last_vacuum,last_autovacuum,last_analyze,last_autoanalyze from pg_stat_all_tables where schemaname = 'pg_catalog' order by 1;
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, schmiddy@gmail.com, lists@deksai.com
Subject: Re: stats collector suddenly causing lots of IO
In-Reply-To: <9738.1271431432@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