Alexey Ermakov <alexey(dot)ermakov(at)postgresql-consulting(dot)com> writes:
> I think we should change that estimation and in case when child node
> expected to return only one row (and really 0 rows) we should use it's
> total_cost as base for estimation of startup_cost.
This would make sense as part of the overall rethinking of startup_cost
but I'm disinclined to do it in isolation. Redefining startup_cost for
just one path type seems likely to create more problems than it solves.
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2016-12-18 18:54:10|
|Subject: Mishandling of right-associated phrase operators in FTS|
|Previous:||From: Michael Meskes||Date: 2016-12-17 15:32:51|
|Subject: Re: BUG #14460: ecpg dynamic describe data types incorrect|