"Robert Wille" <[EMAIL PROTECTED]> writes: > select * from image natural join ancestry where ancestorid=1000000 and > (state & 7::bigint) = 0::bigint;
The planner is not going to have any statistics that allow it to predict the number of rows satisfying that &-condition, and so it's unsurprising if its off-the-cuff guess has little to do with reality. I'd recommend skipping any cute tricks with bit-packing, and storing the state (and any other values you query frequently) as its own column, so that the query looks like select * from image natural join ancestry where ancestorid=1000000 and state = 0; ANALYZE should be able to do a reasonable job with a column that has 8 or fewer distinct values ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend