From: Matt Clark <matt@ymogen.net>
To: josh@agliodbs.com
To: pgsql-performance@postgresql.org
Subject: Re: Is there a reason _not_ to vacuum continuously?
Date: Wed, 17 Sep 2003 21:24:37 +0100
Message-ID: <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net> (raw)
In-Reply-To: <200309171313.31078.josh@agliodbs.com>
> 2) Are you sure that ANALYZE is needed? Vacuum is required
> whenever lots of
> rows are updated, but analyze is needed only when the *distribution* of
> values changes significantly.
You are right. I have a related qn in this thread about random vs. monotonic
values in indexed fields.
> 3) using PG 7.3 or less, you will also need to REINDEX these
> tables+indexes
> often (daily?). This issue will go away in 7.4, which should
> make you an
> early adopter of 7.4.
I understand this needs an exclusive lock on the whole table, which is
simply not possible more than once a month, if that... Workarounds/hack
suggestions are more than welcome :-)
Ta
M
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: matt@ymogen.net, josh@agliodbs.com
Subject: Re: Is there a reason _not_ to vacuum continuously?
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net>
References: <200309171313.31078.josh@agliodbs.com> <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net>
* 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