| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Benjamin Smith <lists(at)benjamindsmith(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Frequency of Analyze? |
| Date: | 2005-10-28 21:51:28 |
| Message-ID: | 20051028215128.GA13187@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Oct 28, 2005 at 01:47:49PM -0700, Benjamin Smith wrote:
> 1) Any problem with running "Analyze" hourly via cron?
Probably not. Analyze usually only reads a small portion of the table.
> 2) Does "Vacuum analyze" also do the actions performed by "Analyze"?
Yes, it does.
> 3) What's the best way to handle indexes when only 1 index is used per table
> in a query, but there are several due to the various constraints on it? Is
> there a way to benefit from all of these other indexes somehow? Is there a
> definitive, detailed book for optimizing PG queries?
8.1 can utilize multiple indexes per table.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-10-28 22:09:46 | Re: Map of Postgresql Users (OT) |
| Previous Message | Oleg Bartunov | 2005-10-28 21:30:33 | Re: tsearch2 setweight |