From: Szu-Ching Peckner <speckner@activedg.com>
To: Bhella Paramjeet-PFCW67 <PBhella@Motorola.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: tuning auto vacuum for highly active tables
Date: Tue, 23 Mar 2010 17:37:56 -0400
Message-ID: <4BA934B4.8090208@activedg.com> (raw)
In-Reply-To: <C84662912D280D4AB5C50100A100F0C50574C753@ct11exm61.ds.mot.com>
References: <C84662912D280D4AB5C50100A100F0C50574C753@ct11exm61.ds.mot.com>
we ran into the same problem, had big table, played with vacuum cost and
delay, but can't shrink too much because of heavy insert and delete.
we ended up with using slony for upgrade, also have data copy from fresh
because of inital replication to shrink our large table, with minimum
controlled downtime.
Bhella Paramjeet-PFCW67 wrote:
>
> Hi All,
>
>
>
> We have a postgres database in which couple of tables get bloated due
> to heavy inserts and deletes. Auto vacuum is running. My question is
> how can I make auto vacuum more aggressive? I am thinking of enabling
> autovacuum_vacuum_cost_delay and autovacuum_vacuum_cost_limit
> parameters. Can anyone suggest how to calculate the appropriate values
> for these parameters and if there are any side effects of enabling
> these parameters. Any help will be highly appreciated.
>
>
>
> Thanks
>
> Paramjeet Kaur
>
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: speckner@activedg.com, PBhella@Motorola.com, pgsql-admin@postgresql.org
Subject: Re: tuning auto vacuum for highly active tables
In-Reply-To: <4BA934B4.8090208@activedg.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