Seamus Abshere writes:
> hey,
> We see a fair number of incorrectly chosen BitmapAnd plans in the wild at
> Faraday... enough that googling the problem ends up at our old posts to this
> mailing list ð. An attractive solution was proposed by Jeff Janes [1]
> - *cost += 0.1 * cpu_operator_cos
hey,
We see a fair number of incorrectly chosen BitmapAnd plans in the wild at
Faraday... enough that googling the problem ends up at our old posts to this
mailing list 😀. An attractive solution was proposed by Jeff Janes [1]
- *cost += 0.1 * cpu_operator_cost * path->rows;
+ *cost += 6 * cpu_o