Re: GEQO and join_collapse_limit correlation
| От | Tom Lane |
|---|---|
| Тема | Re: GEQO and join_collapse_limit correlation |
| Дата | |
| Msg-id | 12214.1515184156@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: GEQO and join_collapse_limit correlation (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>) |
| Ответы |
Re: GEQO and join_collapse_limit correlation
|
| Список | pgsql-performance |
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo.santamaria@gmail.com> writes:
> In an environment with geqo_threshold=1 and join_collapse_limit=1, would
> the planner be GEQO exclusive (and syntactic)?
GEQO's only function, basically, is to search for the join order to use.
If you're constraining the join order completely with
join_collapse_limit=1 then forcing the GEQO path to be taken would just
add pointless overhead. (If it does anything at all ... I don't remember
the logic exactly but we might be bright enough not to bother with GEQO in
such a situation, regardless of geqo_threshold.)
regards, tom lane
В списке pgsql-performance по дате отправления: