Re: Too many BitmapAnds in the wild

2018-09-17 Thread Tom Lane
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

Too many BitmapAnds in the wild

2018-09-17 Thread Seamus Abshere
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