From: Josh Berkus <josh@agliodbs.com>
To: Aaron Held <aaron@MetroNY.com>
Cc: Chris Ruprecht <chrup@earthlink.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Performance w/ multiple WHERE clauses
Date: Mon, 23 Sep 2002 19:14:52 -0700
Message-ID: <200209231914.52643.josh@agliodbs.com> (raw)
In-Reply-To: <3D8F17B5.60902@MetroNY.com>
References: <5.1.1.6.2.20020918111926.00a82058@mail.nashlinux.com>
<200209201455.30054.josh@agliodbs.com>
<3D8F17B5.60902@MetroNY.com>
Aaron,
> This database gets a monthly update and it read only until the next
> update. I ANALYZE once after each update. Since the data does not
> change I should not need to ANALYZE again afterwards.
Actually, if the database is read-only between updates, you should:
ANALYZE
VACUUM FULL FREEZE
... between data updates, which will give you the best performance possible.
But not if the data is actually going to be edited, even slightly.
See the online manual entries about VACUUM for an explanation.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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-sql@postgresql.org
Cc: josh@agliodbs.com, aaron@MetroNY.com, chrup@earthlink.net
Subject: Re: Performance w/ multiple WHERE clauses
In-Reply-To: <200209231914.52643.josh@agliodbs.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