thx for the answer. - What is the problem, i.e. what behaviour you expect? - How much data is the table? - What portion of it matches the conditions? - What is the index definition? i think in my first post i provided most of these details but -> 1) what i expect is to be able to understand why the index is not used and if possibly to use it somehow, or recreate it in a better way 2) the table has 115 GB and about 700 milion rows 3) the result should be less than 10 millions rows 4) the index is a btree i tried to disable seq_scan and the query plan was changed and used another index and not the one i wanted. -- View this message in context: http://postgresql.1045698.n5.nabble.com/cannot-use-multicolumn-index-tp4802634p4803198.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
