Re: Bunch o' dead code in GEQO

Поиск
Список
Период
Сортировка
Искать
От
scott.marlowe
Тема
Re: Bunch o' dead code in GEQO
Дата
Msg-id
Pine.LNX.4.33.0401220929100.25073-100000@css120.ihs.com
Ответ на
Список
Дерево обсуждения
Bunch o' dead code in GEQO Tom Lane <tgl@sss.pgh.pa.us>
Re: Bunch o' dead code in GEQO "scott.marlowe" <scott.marlowe@ihs.com>
Re: Bunch o' dead code in GEQO Tom Lane <tgl@sss.pgh.pa.us>
Re: Bunch o' dead code in GEQO Neil Conway <neilc@samurai.com>
Re: Bunch o' dead code in GEQO Tom Lane <tgl@sss.pgh.pa.us>
Re: Bunch o' dead code in GEQO Neil Conway <neilc@samurai.com>
Re: Bunch o' dead code in GEQO Tom Lane <tgl@sss.pgh.pa.us>
Re: Bunch o' dead code in GEQO "scott.marlowe" <scott.marlowe@ihs.com>
Re: Bunch o' dead code in GEQO Tom Lane <tgl@sss.pgh.pa.us>
On Thu, 22 Jan 2004, Tom Lane wrote:

> "scott.marlowe"  writes:
> > On Wed, 21 Jan 2004, Tom Lane wrote:
> >> The GEQO planner module contains six different recombination algorithms,
> 
> > considering the recent discussion about REALLY slow query planning by the 
> > GEQO module, it might be worth testing each one to see which works best 
> > before lopping them off.
> 
> I'm assuming that the original author of the GEQO code already did that
> testing ...

Hmmm.  I was figuring he wasn't sure so he left them in for other people 
to test.  Is this a part of the code that eats up much time, or something 
simple and fast that isn't part of the "GEQO takes 8 seconds to plan" 
problem?


В списке pgsql-hackers по дате отправления
От: Andrew Dunstan
Дата:
От: Tom Lane
Дата:
Сообщение: Re: Bunch o' dead code in GEQO
FAQ