| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Leonardo F <m_lists(at)yahoo(dot)it> |
| Cc: | APseudoUtopia <apseudoutopia(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Order of Daily VACUUM, CLUSTER, REINDEX |
| Date: | 2010-03-19 17:05:17 |
| Message-ID: | 20100319170517.GB3301@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Leonardo F escribió:
> > VACUUM ANALYZE;
> > CLUSTER;
> > REINDEX DATABASE "database";
>
> ANALYZE has to go after CLUSTER; and CLUSTER already
> vacuums the tables (I'm not 100% sure though). CLUSTER also
> reindexes the whole table, so there's no need for another REINDEX.
>
> I think the right way of doing it would be:
>
> CLUSTER;
> ANALYZE; (no "vacuum analyze", just "analyze").
Note that cluster only clusters tables that have been previously
clustered. So you still need to vacuum tables that are not clustered.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | justin@magwerks.com | 2010-03-19 18:12:52 | Re: [GENERAL] MS Access 2007 update write conflict problem & resolution |
| Previous Message | Jay | 2010-03-19 16:36:21 | Re: Help me with this tricky join |