Re: Shouldn't we have a way to avoid "risky" plans? - Mailing list pgsql-performance

From Josh Berkus
Subject Re: Shouldn't we have a way to avoid "risky" plans?
Date
Msg-id 4D8A581D.5080704@agliodbs.com
Whole thread Raw
In response to Re: Shouldn't we have a way to avoid "risky" plans?  (Claudio Freire <klaussfreire@gmail.com>)
Responses Re: Shouldn't we have a way to avoid "risky" plans?  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-performance
On 3/23/11 10:35 AM, Claudio Freire wrote:
>  *  consider plan bailout: execute a tempting plan, if it takes too
> long or its effective cost raises well above the expected cost, bail
> to a safer plan

That would actually solve this particular case.  It would still require
us to have some definition of "safer" though.

--
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

pgsql-performance by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: buffercache/bgwriter
Next
From: Laszlo Nagy
Date:
Subject: Slow query on CLUTER -ed tables