From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Subject: Autovacuum daemon functionality questions
Date: Thu, 8 Apr 2010 20:01:05 +0530
Message-ID: <00c001cad728$22f92f20$68eb8d60$@com> (raw)
Hi,
I'm using PostgreSQL 8.2.
I want to configure autovacuum daemon process in our production server in an
efficient way and take advantage of this daemon to perform vacuum and
analyze more aggressively.
I also read about autovacuum daemon at
http://www.postgresql.org/docs/8.2/interactive/routine-vacuuming.html
My questions are:
1. Why need to have 2 parameters (base threshold and scale factor) to define
the threshold value, when either one of the parameter is more than enough to
define the threshold value. Can you explain the significance of having both
parameters. What is the real-time advantage of this?
2. Documentation says ".... If the number of obsolete tuples since the last
VACUUM exceeds the "vacuum threshold", the table is vacuumed ...".
I also know about this table "pg_stat_user_tables" which has columns
n_tup_ins, n_tup_upd, n_tup_del, last_autovaccum and last_autoanalyze.
Since INSERT, UPDATE and DELETE count gets incremented everytime and do not
reset after running autovacuum/autoanalyze, how does autovacuum identifies
obsolete tuples since last VACUUM from this entries.
3. Is there a way to see autovacuum daemon log entries?
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-admin@postgresql.org
Cc: gnanam@zoniac.com
Subject: Re: Autovacuum daemon functionality questions
In-Reply-To: <00c001cad728$22f92f20$68eb8d60$@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