On 2019-Jul-01, David Rowley wrote:
> One thing we could look at would be to charge an additional
> cpu_tuple_cost per outer row for all joins except semi, anti and
> unique joins. This would account for the additional lookup for
> another matching row which won't be found and cause the planner to
> slightly favour keeping the unique rel on the inner side of the join,
> when everything else is equal.
So does this proposal fix the problem that David was describing earlier?
If it does, Tom, would you like to get this finalized and pushed?
I've bcc'ed someone who might be interested in chiming in and/or helping
out. Please look here:
https://postgr.es/m/153683552113.22350.18441286362867559841@wrigleys.postgresql.org
Thanks,
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
