From: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Fri, 17 Oct 2003 17:11:59 -0600
Message-ID: <16272.30527.120343.547492@jump.bivio.com> (raw)
In-Reply-To: <cm90pvsbml6qdpe9el3qm66ogj7cpdk5ar@email.aon.at>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<3F9006BF.40906@persistent.co.in>
<16272.4154.489000.227676@gargle.gargle.HOWL>
<cm90pvsbml6qdpe9el3qm66ogj7cpdk5ar@email.aon.at>
Manfred Koizar writes:
> ISTM you are VACCUMing too aggressively. You are reclaiming less than
> 1% and 0.005%, respectively, of tuples. I would increase FSM settings
> to ca. 1000 fsm_relations, 100000 fsm_pages and VACUUM *less* often,
> say every two hours or so.
I did this. We'll see how it goes.
> ... or configure autovacuum to VACUUM a table when it has 10% dead
> tuples.
This solution doesn't really fix the fact that VACUUM consumes the
disk while it is running. I want to avoid the erratic performance on
my web server when VACUUM is running.
mfg,
Rob
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: nagler@bivio.biz
Subject: Re: vacuum locking
In-Reply-To: <16272.30527.120343.547492@jump.bivio.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