From: Josh Kupershmidt <schmiddy@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chris <lists@deksai.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector suddenly causing lots of IO
Date: Fri, 16 Apr 2010 14:35:56 -0400
Message-ID: <m2w4ec1cf761004161135ka272c184u2f0dd8a0c8460d5d@mail.gmail.com> (raw)
In-Reply-To: <4BC8A91D.9030709@2ndquadrant.com>
References: <20100413170105.GA29571@chris-laptop.a2hosting.com>
<25952.1271370711@sss.pgh.pa.us>
<z2s4ec1cf761004160739w3ac5511jd39263dd043e2da6@mail.gmail.com>
<9738.1271431432@sss.pgh.pa.us>
<g2t4ec1cf761004160830q5dff4315rcc0294d342999c35@mail.gmail.com>
<10082.1271432484@sss.pgh.pa.us>
<h2p4ec1cf761004160931r47cf4949o9a2fc14529c17ab1@mail.gmail.com>
<11152.1271436528@sss.pgh.pa.us>
<m2w4ec1cf761004161043yd59174a5h9fb011a16608d96d@mail.gmail.com>
<4BC8A91D.9030709@2ndquadrant.com>
On Fri, Apr 16, 2010 at 2:14 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> Josh Kupershmidt wrote:
>>
>> SELECT name, current_setting(name), source FROM pg_settings WHERE
>> source != 'default' AND name ILIKE '%vacuum%';
>> name | current_setting | source
>> ----------------------+-----------------+--------------------
>> vacuum_cost_delay | 200ms | configuration file
>> vacuum_cost_limit | 100 | configuration file
>> vacuum_cost_page_hit | 6 | configuration file
>>
>> Hopefully changing those three vacuum_cost_* params will speed up the
>> manual- and auto-vacuums..
>
> Those only impact manual VACUUM statements. There's a different set with
> names like autovacuum_vacuum_cost_delay that control the daemon. You can
> set those to "-1" in order to match the regular VACUUM, but that's not the
> default.
It looks like the default which I have of autovacuum_vacuum_cost_limit
= -1, which means it's inheriting the vacuum_cost_limit of 100 I had
set. I'll try bumping vacuum_cost_limit up to 1000 or so.
> You really need to sort out the max_fsm_pages setting too, because until
> that issue goes away these tables are unlikely to ever stop growing. And,
> no, you can't use CLUSTER on the system tables to clean those up.
I have max_fsm_pages = 524288 , but from the hints in the logfiles
this obviously needs to go up much higher. And it seems the only way
to compact the pg_catalog tables is VACUUM FULL + REINDEX on 8.3 -- I
had tried the CLUSTER on my 9.0 machine and wrongly assumed it would
work on 8.3, too.
Josh
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: schmiddy@gmail.com, greg@2ndquadrant.com, tgl@sss.pgh.pa.us, lists@deksai.com
Subject: Re: stats collector suddenly causing lots of IO
In-Reply-To: <m2w4ec1cf761004161135ka272c184u2f0dd8a0c8460d5d@mail.gmail.com>
References: <20100413170105.GA29571@chris-laptop.a2hosting.com> <25952.1271370711@sss.pgh.pa.us> <z2s4ec1cf761004160739w3ac5511jd39263dd043e2da6@mail.gmail.com> <9738.1271431432@sss.pgh.pa.us> <g2t4ec1cf761004160830q5dff4315rcc0294d342999c35@mail.gmail.com> <10082.1271432484@sss.pgh.pa.us> <h2p4ec1cf761004160931r47cf4949o9a2fc14529c17ab1@mail.gmail.com> <11152.1271436528@sss.pgh.pa.us> <m2w4ec1cf761004161043yd59174a5h9fb011a16608d96d@mail.gmail.com> <4BC8A91D.9030709@2ndquadrant.com> <m2w4ec1cf761004161135ka272c184u2f0dd8a0c8460d5d@mail.gmail.com>
* 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