From: Tobias Brox <tobias@nordicbet.com>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
Date: Wed, 27 Sep 2006 18:13:29 +0200
Message-ID: <20060927161329.GB25630@oppetid.no> (raw)
In-Reply-To: <451AA1FE.9050704@axa.it>
References: <451AA1FE.9050704@axa.it>
[Edoardo Ceccarelli - Wed at 06:08:30PM +0200]
> We also activated the autovacuum feature to give it a try and that's
> were our problems started.
(...)
> How can I configure the vacuum to run after the daily batch insert/update?
I think you shouldn't use autovacuum in your case.
We haven't dared testing out autovacuum yet even though we probably
should, so we're running vacuum at fixed times of the day. We have a
very simple script to do this, the most important part of it reads:
echo "vacuum verbose analyze;" | psql $DB_NAME > $logdir/$filename 2>&1
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: tobias@nordicbet.com, eddy@axa.it, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
In-Reply-To: <20060927161329.GB25630@oppetid.no>
* 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