Hi, I query is using Index scan instead of Bitmap Index Scan because it "thinks" that the number of rows returned will be low (12). In fact, the number of rows returned is 120. This happens because there are some WHERE conditions that check cross-tables values (something like taba.col1 < tabb.col2) . Since Postgresql doesn't know (I guess) anything about cross-table values statistics, how are the "rows" values calculated? Is there any way I can force the planner to use bitmap index scan? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
