Re: Multi-pass planner - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Multi-pass planner
Date
Msg-id 005001ce31b8$10b6c500$32244f00$@kapila@huawei.com
Whole thread Raw
In response to Re: Multi-pass planner  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Friday, April 05, 2013 1:59 AM Robert Haas wrote:
> On Thu, Apr 4, 2013 at 2:53 PM, Dimitri Fontaine
> <dimitri@2ndquadrant.fr> wrote:
> > Robert Haas <robertmhaas@gmail.com> writes:
> >> for estimate_worstcase_fraction.  So, when computing the cost of a
> >> path, we'd compute our current expected-case estimate, and also a
> >> worst-case estimate, and then compute the final cost as:
> >
> > There also was the idea for the executor to be able to handle
> alternate
> > plans and some heuristic to determine that the actual cost of running
> a
> > plan is much higher than what's been estimated, so much so as to
> switch
> > to starting from scratch with the other plan instead.
> 
> Yeah.  The thing is, if the plan has any side effects, that's not
> really an option.  And even if it doesn't, it may throw away a lot of
> work.  

Why to throw away all the work, it could as well try to repair the plan or
even if plan repair is not possible, it can keep multiple plans and 
next time can try to choose best among available one's.


With Regards,
Amit Kapila.




pgsql-hackers by date:

Previous
From: Rodrigo Barboza
Date:
Subject: Re: Why there is a PG_GETARG_UINT32 and PG_RETURN_UINT32?
Next
From: Brendan Jurd
Date:
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)