From: Shridhar Daithankar <ghodechhap@ghodechhap.net>
To: Dmitry Karasik <dmitry@karasik.eu.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: VACUUM ANALYZE downgrades performance
Date: Thu, 2 Dec 2004 22:08:57 +0530
Message-ID: <200412022208.57760.ghodechhap@ghodechhap.net> (raw)
In-Reply-To: <84wtw0d6q2.fsf@plab.ku.dk>
References: <84fz2ra2gy.fsf_-_@plab.ku.dk>
<41AC94CC.1020602@idigx.com>
<84wtw0d6q2.fsf@plab.ku.dk>
On Thursday 02 Dec 2004 9:37 pm, Dmitry Karasik wrote:
> Hi Thomas!
>
> Thomas> Look at the ACTUAL TIME. It dropped from 0.029ms (using the index
> Thomas> scan) to 0.009ms (using a sequential scan.)
>
> Thomas> Index scans are not always faster, and the planner/optimizer knows
> Thomas> this. VACUUM ANALYZE is best run when a large proportion of data
> Thomas> has been updated/loaded or in the off hours to refresh the
> Thomas> statistics on large datasets.
>
> While I agree that generally this is true, look how stupid this
> behavior looks in this particular case: A developer creates a table
> and index, knowing that the table will be large and will be intensively
> used. An admin runs 'VACUUM ANALYZE' when table is occasionally empty,
> and next, say, 1 day, until another 'VACUUM ANALYZE' starts, the index
> is simply not used! Sure you don't suppose to run 'VACUUM ANALYZE' every
> 5 minutes as a solution, right?
Why not? If the updates are frequent enough, that is *the* solution.
But you could always use autovacuum daemon in most case.
HTH
Shridhar
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: ghodechhap@ghodechhap.net, dmitry@karasik.eu.org
Subject: Re: VACUUM ANALYZE downgrades performance
In-Reply-To: <200412022208.57760.ghodechhap@ghodechhap.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