From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Patric <lists(at)p-dw(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Reasonable amount of indices |
Date: | 2007-09-06 22:09:40 |
Message-ID: | 20070906220940.GN8709@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Patric wrote:
> My Question now is: Is it wise to do so, and create hundreds or maybe
> thousands of Indices
> which partition the table for the selections.
No, this is not helpful -- basically what you are doing is taking the
first level (the first couple of levels maybe) of the index out of it,
and charging the planner with the selection of which one is the best for
each query.
Of course, I am assuming you were simplifing your queries and don't
actually store the name of the continent etc on each on every row.
Because if you actually do that, then there's your first oportunity for
actual optimization (which happens to be a more normalized model), far
more effective than the partial indexes you are suggesting.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-09-06 22:35:11 | Re: SAN vs Internal Disks |
Previous Message | Alvaro Herrera | 2007-09-06 21:21:16 | Re: Performance on 8CPU's and 32GB of RAM |