From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Better index stategy for many fields with few values |
Date: | 2006-04-13 09:33:53 |
Message-ID: | 443E1B01.5060804@logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi, Jim,
Jim C. Nasby wrote:
>>>I was also thinking about about using a functional index.
>>If there's a logical relation between those values that they can easily
>>combined, that may be a good alternative.
> How would that be any better than just doing a multi-column index?
10 different values per column, and 20 columns are 10^20 value combinations.
Partitioning it for the first column gives 10^19 combinations which is
smaller than 2^64, and thus fits into a long value.
And I just guess that a 10-partition functional index on a long value
could perform better than a multi-column index on 20 columns of
character(10), if only because it is approx. 1/25th in size.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2006-04-13 09:51:22 | Re: Better index stategy for many fields with few values |
Previous Message | Bruce Momjian | 2006-04-13 08:39:35 | Re: bad performance on Solaris 10 |