Re: enable_joinremoval

Поиск
Список
Период
Сортировка
От Alex Hunsaker
Тема Re: enable_joinremoval
Дата
Msg-id 34d269d41003291254p1e42b3a8n8cab1f1df04252db@mail.gmail.com
обсуждение исходный текст
Ответ на Re: enable_joinremoval  (Simon Riggs <simon@2ndQuadrant.com>)
Ответы Re: enable_joinremoval  (Simon Riggs <simon@2ndQuadrant.com>)
Re: enable_joinremoval  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Mon, Mar 29, 2010 at 13:41, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Uhh... they wont be in the explain output...  Seems simple enough.
>
> That is exactly what I replied, though nobody felt that was a great
> answer.

Maybe I missed it, but why exactly do they care?  About the only
reason I can think *i* would care is:  If I was running the same SQL
on multiple database products (like mysql) and thought "Sweet now I
can use this new feature to cleanup my sql so it runs better on
product X or version of postgres Y".  Is there some other reason other
than it would be _cool_ to know?  Or is it FUD that it might be buggy
and so they wish to be able to turn it off?

It comes to mind you can probably do this with an plannerhook
(whatever happened to those hooks to auto create/recommend indexes?)


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

Предыдущее
От: Dimitri Fontaine
Дата:
Сообщение: Re: Proposal: Add JSON support
Следующее
От: Tom Lane
Дата:
Сообщение: Re: enable_joinremoval