Alex Pires de Camargo <acamargo@gmail.com> writes:
> In order to plan the best workarounds, this has a chance to be fixed in a
> near future?
I wouldn't recommend holding your breath. Someone would have to get
interested in the problem and design/write/test a better cost model;
and if/when that happens, we'd be unlikely to back-patch such a change
into existing release branches.
regards, tom lane
