Alvaro Herrera <alvherre@xxxxxxxxxxxxxxxxx> writes: > Seems like the problem is that it is not pushing the "status IN" > condition as part of the index condition for some reason, and instead > using it as a filter. Maybe something to do with the selectivity of > that clause? No, AFAIR the planner will *always* include every possibly relevant condition for a given index. If the condition is useless or nearly so, that might prompt it to pick a different index instead, but not to omit the indexqual. I'm thinking it's not believing it can use the status condition with that index, perhaps for datatype reasons. What is status declared as, exactly? Also, what PG version is this? regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
