From: Ray Stell <stellr@cns.vt.edu>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: Galy Lee <lee.galy@oss.ntt.co.jp>
Cc: pgsql-performance@postgresql.org, Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] how to plan for vacuum?
Date: Thu, 25 Jan 2007 11:33:29 -0500
Message-ID: <20070125163329.GD19599@cns.vt.edu> (raw)
In-Reply-To: <45B8D521.8010405@commandprompt.com>
References: <45B6F0A8.1050705@oss.ntt.co.jp>
<20070125033917.GD64372@nasby.net>
<20070125035202.GI26006@alvh.no-ip.org>
<45B8D521.8010405@commandprompt.com>
On Thu, Jan 25, 2007 at 08:04:49AM -0800, Joshua D. Drake wrote:
>
> It really depends on the system. Most of our systems run anywhere from
> 10-25ms. I find that any more than that, Vacuum takes too long.
How do you measure the impact of setting it to 12 as opposed to 15?
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: stellr@cns.vt.edu, jd@commandprompt.com, jim@nasby.net, lee.galy@oss.ntt.co.jp, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] how to plan for vacuum?
In-Reply-To: <20070125163329.GD19599@cns.vt.edu>
* 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