Re: from_collapse_limit vs. geqo_threshold
От | Tom Lane |
---|---|
Тема | Re: from_collapse_limit vs. geqo_threshold |
Дата | |
Msg-id | 8847.1242906656@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: from_collapse_limit vs. geqo_threshold (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: from_collapse_limit vs. geqo_threshold
|
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: > Robert, >> It appears that this statement has been in our documentation since Tom >> Lane added FROM_COLLAPSE_LIMIT (back then, it was capitalized) on >> January 25, 2003 (9bf97ff426de9), but I can't find any justification >> for it anywhere. I think we either need to justify this advice, or >> remove it. > ... trying to remember why I wrote that ... what would happen if > FROM_COLLAPSE_LIMIT was *more* than GEQO_THRESHOLD? I think I wrote it, not you. The point of the advice is to keep subquery collapsation (hm, what's the right noun form? Need caffeine) from turning a non-GEQO query into a GEQO one, and thus subjecting you to unpredictable plans. Maybe the resulting plans would be better on average, or maybe they wouldn't, but in any case they'd be unpredictable. regards, tom lane
В списке pgsql-hackers по дате отправления: