I'd like to create a ToDo item for "loose index scans" or "skip scans", when the lead column has low cardinality and is not used in the where clause. This case can potentially be optimized by using the index as if it were a collection of N "partitioned" indexes, where N is the cardinality of the lead column. Any objections?
I don't really have a detailed plan on how to do it. I expect the planner part would be harder than the execution part. See "[PERFORM] Loose Index Scans by Planner" thread. Thanks, Jeff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
