Re: Mini improvement: statement_cost_limit

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Mini improvement: statement_cost_limit
Дата
Msg-id 1217882983.3934.548.camel@ebony.t-mobile.de.
обсуждение исходный текст
Ответ на Re: Mini improvement: statement_cost_limit  (Robert Treat <xzilla@users.sourceforge.net>)
Ответы Re: Mini improvement: statement_cost_limit  (Robert Treat <xzilla@users.sourceforge.net>)
Re: Mini improvement: statement_cost_limit  (Decibel! <decibel@decibel.org>)
Список pgsql-hackers
On Mon, 2008-08-04 at 14:35 -0400, Robert Treat wrote:
> On Monday 04 August 2008 03:50:40 daveg wrote:

> And you'll note, I specifically said that a crude tool is better than
> nothing. But your completely ignoring that a crude tool can often
> end-up as a foot-gun once relased into the wild. 

The proposal is for an option with no consequences when turned off. We
respect your right not to use it. What is the danger exactly? 

If we cancel stupid queries before people run them, everybody is a
winner. Even the person who submitted the stupid query, since they find
out faster.

Sure, its an estimate, but it's got to be a based upon an estimate if it
acts *before* it runs. And surely there is no better estimate of the
cost than the plan cost?

It doesn't stop anyone from putting in resource limits, later.

We'll have to do something with enable_seqscan, BTW, chaps.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Mini improvement: statement_cost_limit
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Mini improvement: statement_cost_limit