From: Jim C. Nasby <jim@nasby.net>
To: Galy Lee <lee.galy@oss.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] how to plan for vacuum?
Date: Thu, 25 Jan 2007 10:22:47 -0600
Message-ID: <20070125162246.GF64372@nasby.net> (raw)
In-Reply-To: <45B88C02.3010802@oss.ntt.co.jp>
References: <45B6F0A8.1050705@oss.ntt.co.jp>
<20070125033917.GD64372@nasby.net>
<20070125035202.GI26006@alvh.no-ip.org>
<20070125035741.GE64372@nasby.net>
<45B88C02.3010802@oss.ntt.co.jp>
On Thu, Jan 25, 2007 at 07:52:50PM +0900, Galy Lee wrote:
> It is very hard for any normal user to set this correctly. I think the
> experience / trial-and-error approach is awful for the user, every DBA
> need to be an expert of vacuum to keep the system stable. For vacuum is
> still a big threat to the performance, a more intelligent way is needed.
Agreed.
> So I have proposed the "vacuum in time" feature in previous; just let
> vacuum know how long can it runs, and then it will minimize the impact
> in the time span for you. Some argue that it should not have the
> maintenance window assumption, but the most safely way is to run in the
> maintenance window.
Most systems I work on don't have a maintenance window. For those that
do, the window is at best once a day, and that's nowhere near often
enough to be vacuuming any database I've run across. I'm not saying they
don't exist, but effort put into restricting vacuums to a maintenance
window would serve very few people. It'd be much better to put effort
into things like piggyback vacuum.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
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: jim@nasby.net, lee.galy@oss.ntt.co.jp, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] how to plan for vacuum?
In-Reply-To: <20070125162246.GF64372@nasby.net>
* 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