"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> Are Arjen's tests on prepared queries?
> Does that change anything? We shy
> away from indexes on prepared queries too much already, important when
> the consequence of doing so is an O(N) seqscan rather than an O(logN)
Changing that will require far more extensive changes than twiddling a
few cost estimates.
> The cost of initiating an index scan is a cause for concern, but it
> seems reasonable to get it accurate. I'd like to perform some of that
> work at planning time, not at scan time, when it is possible for us to
> do so. Simple indexed, planned queries shouldn't need to pay that cost
Isn't this opinion in direct contradiction to your previous paragraph?
If you want the thing to be more flexible about plans involving unknown
parameter values, then you have to push work towards the runtime end,
not towards the planner.
regards, tom lane
In response to
pgsql-patches by date
|Next:||From: Simon Riggs||Date: 2006-12-11 21:00:37|
|Subject: Re: Proposed fixes for planner regressions from Junetorelease|
|Previous:||From: Simon Riggs||Date: 2006-12-11 19:59:38|
|Subject: Re: Proposed fixes for planner regressions from June torelease|