From: Galy Lee <lee.galy@oss.ntt.co.jp>
To: pgsql-performance@postgresql.org
Cc: jim@nasby.net
Subject: Re: how to plan for vacuum?
Date: Thu, 25 Jan 2007 19:29:20 +0900
Message-ID: <45B88680.4040500@oss.ntt.co.jp> (raw)
In-Reply-To: <20070125033917.GD64372@nasby.net>
References: <45B6F0A8.1050705@oss.ntt.co.jp>
<20070125033917.GD64372@nasby.net>
Jim C. Nasby wrote:
> On Wed, Jan 24, 2007 at 02:37:44PM +0900, Galy Lee wrote:
>> 1. How do we know if autovacuum is enough for my application, or should
>> I setup a vacuum manually from cron for my application?
>
> Generally I trust autovac unless there's some tables where it's critical
> that they be vacuumed frequently, such as a queue table or a web session
> table.
So how much can we trust autovac? I think at least the following cases
can not be covered by autovac now:
- small but high update tables which are sensitive to garbage
- very big tables which need a long time to be vacuumed.
- when we need to adjust the the max_fsm_page
>> 2. How to set the GUC parameters for autovacuum?
>> There are two sets of parameters for autovacuum:
>> - vacuum threshold and scale factor (500/0.2)
>> ?$B!! - analyze threshold and scale factor(250/0.1)
>> Is there any guideline to set these parameters? When does it need to
>> change the default values?
>
> I find those are generally pretty good starting points; just bear in
> mind that it means 20% dead space.
so what is the principle to set them?
- keep dead space lower than some disk limit
- or keep the garbage rate lower than fillfactor
or any other general principle?
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: lee.galy@oss.ntt.co.jp, jim@nasby.net
Subject: Re: how to plan for vacuum?
In-Reply-To: <45B88680.4040500@oss.ntt.co.jp>
* 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