Search Postgresql Archives

Re: B-tree performance improvements in 8.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dick Kniep <dick@xxxxxxxx> writes:

> Does this mean that if you have a table that has many rows, and 95% of the 
> rows contain a NULL value for a field, that indexing will be useless, because 
> it will always do a tablescan?

Any time you have 95% of the rows of the table with the same value you're
probably going to have to think harder than usual about indexing strategies.
You might consider constructing your index with "WHERE a IS NOT NULL" since
otherwise 95% of your index is going to be full of records that aren't
selective enough to be useful anyways.

If you access your table with "WHERE a = ?" then it will undoubtedly use the
index effectively. You're accessing less than 5% (presumably much less), so
the index is useful.

-- 
greg



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux