Re: Shouldn't we have a way to avoid "risky" plans?

Поиск
Список
Период
Сортировка
От Claudio Freire
Тема Re: Shouldn't we have a way to avoid "risky" plans?
Дата
Msg-id AANLkTi=RXUSrCxqz3=BkAiixuenu2gf-K+W15Wz4McXH@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Shouldn't we have a way to avoid "risky" plans?  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Shouldn't we have a way to avoid "risky" plans?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Laszlo Nagy
Дата:
Сообщение: Slow query on CLUTER -ed tables
Следующее
От: Justin Pitts
Дата:
Сообщение: Re: Shouldn't we have a way to avoid "risky" plans?