Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Дата
Msg-id 28261.1257782223@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I've stopped the query more than 10 times now and EVERY SINGLE ONE
> finds it in list_concat_unique_ptr().  :-(

Too bad you don't have debug symbols ... it'd be interesting to see
how long that list is.

> It's also using about 12x as much RAM as the GEQO version.

No surprise.  GEQO is designed to constrain its memory use, the
exhaustive planner not so much.
        regards, tom lane


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

Предыдущее
От: Sonu
Дата:
Сообщение: Re: Specific names for plpgsql variable-resolution control options?
Следующее
От: Jan Otto
Дата:
Сообщение: Re: drop tablespace error: invalid argument