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

From Claudio Freire
Subject Re: Shouldn't we have a way to avoid "risky" plans?
Date
Msg-id AANLkTi=RXUSrCxqz3=BkAiixuenu2gf-K+W15Wz4McXH@mail.gmail.com
Whole thread Raw
In response to Re: Shouldn't we have a way to avoid "risky" plans?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Shouldn't we have a way to avoid "risky" plans?
List pgsql-performance
On Wed, Mar 23, 2011 at 5:29 PM, Josh Berkus <josh@agliodbs.com> wrote:
> 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.

In my head, safer = better worst-case performance.

pgsql-performance by date:

Previous
From: Laszlo Nagy
Date:
Subject: Slow query on CLUTER -ed tables
Next
From: Justin Pitts
Date:
Subject: Re: Shouldn't we have a way to avoid "risky" plans?