| From: | Jonathan Vanasco <postgres(at)2xlp(dot)com> |
|---|---|
| To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: sql indexing suggestions needed |
| Date: | 2007-03-21 02:01:16 |
| Message-ID: | 3C08C9F4-E220-4E5D-B1C3-621D2890A703@2xlp.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mar 20, 2007, at 3:24 PM, Ron Johnson wrote:
> How many *distinct* values are there in int_c? What percentage of
> them match "int_c <= 10"?
right now there are 14, and 80% match -- but next week that number
will be 20 , 60% ... and so on
> Same questions, but for int_h.
same answer
> If int_h is relatively unique, then this index might help:
> (INT_H, INT_C)
If that helps, try
> (INT_H, INT_C, BOOL_A, BOOL_B, BOOL_D, BOOL_E, BOOL_G, BOOL_I)
i'll try both, thanks.
the current 'super index' works - i'm more worried for speed right
now than disk space , so its worth physical overhead.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Klint Gore | 2007-03-21 02:02:21 | Re: Approximate join on timestamps |
| Previous Message | Matthew.Pettis@gmail.com | 2007-03-21 01:48:15 | Using PostgreSQL to archive personal email |