| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Aaron Held <aaron(at)MetroNY(dot)com> |
| Cc: | Chris Ruprecht <chrup(at)earthlink(dot)net>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Performance w/ multiple WHERE clauses |
| Date: | 2002-09-24 02:14:52 |
| Message-ID: | 200209231914.52643.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hasler | 2002-09-24 02:20:52 | Re: [GENERAL] CURRENT_TIMESTAMP |
| Previous Message | Alvaro Herrera | 2002-09-24 02:11:48 | Re: [SQL] Monitoring a Query |