Re: query plan and parenthesis
От | Christoph Haller |
---|---|
Тема | Re: query plan and parenthesis |
Дата | |
Msg-id | 3EE9B425.B8F1E9BA@rodos.fzk.de обсуждение исходный текст |
Ответ на | query plan and parenthesis (Jan Poslusny <pajout@gingerall.cz>) |
Ответы |
Re: query plan and parenthesis
|
Список | pgsql-general |
> I have following view definition given by '\d' command: SELECT t1.col1 > FROM ((table1 t1 JOIN table2 t2 ON ((t1.id = t2.id))) JOIN table3 t3 ON > ((t2.some = t3.some))); > Is query planner able to optimize order of joining (t1, t2), t3 or must > join with order described by parenthesis ? This is very important for > joining small (50 rows) and huge (5M rows) tables. > The postgresql-7.3.2 documentation says: Finally, a FROM item can be a JOIN clause, which combines two simpler FROM items. (Use parentheses if necessary to determine the order of nesting.) So, I say, anyway if the planner is able to or not, if you know in advance what order of nesting is optimal, use parentheses. On the other hand, after doing a VACUUM, you can always do an EXPLAIN to see how the planner will act. Regards, Christoph
В списке pgsql-general по дате отправления: