pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Galy Lee <lee.galy@oss.ntt.co.jp>
To: pgsql-performance@postgresql.org
Subject: how to plan for vacuum?
Date: Wed, 24 Jan 2007 14:37:44 +0900
Message-ID: <45B6F0A8.1050705@oss.ntt.co.jp> (raw)

Hi,

For I can not find too much information about how to use vacuum, I want
to ask some general information about the guideline of vacuum planning.

1.  How do we know if autovacuum is enough for my application, or should
    I setup a vacuum manually from cron for my application?

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)
　  - 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?
　
3. How to tune cost-based delay vacuum?
I had searched in performance list; it seems that most of the practices
are based on experience / trial-and-error approach to meet the
requirement of disk utilization or CPU utilization. Is there any other
guild line to set them?

For when autovacuum is turned on by default, if the parameters for
vacuum have not been set well, it will make the system rather unstable.
So I just wonder if we should setup a section in the manual about the
tips of vacuum, then many users can easily set the vacuum parameters for
their system.

Best Regards
Galy Lee
NTT OSS Center

view thread (13+ messages)  latest in thread

Message-ID: <45B6F0A8.1050705@oss.ntt.co.jp>
Permalink:  ../45B6F0A8.1050705@oss.ntt.co.jp/
Also on:    postgresql.org/message-id/45B6F0A8.1050705@oss.ntt.co.jp

copy link · copy postgr.es

reply

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
  Subject: Re: how to plan for vacuum?
  In-Reply-To: <45B6F0A8.1050705@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