Re: *_collapse_limit, geqo_threshold
| От | Tom Lane |
|---|---|
| Тема | Re: *_collapse_limit, geqo_threshold |
| Дата | |
| Msg-id | 286.1247005999@sss.pgh.pa.us обсуждение |
| Ответ на | Re: *_collapse_limit, geqo_threshold (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: *_collapse_limit, geqo_threshold
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Jul 7, 2009, at 4:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> My own thought is that from_collapse_limit has more justification,
> That's pretty much where I am with it, too. The feature I was
> referring to was not the collapse limits, but the ability to
> explicitly specify the join order, which perhaps could be a useful
> tool for reducing planning time or coping with bad estimates if you
> could do it for only some of the joins in the query, but which we're
> instead proposing to keep as an all-or-nothing flag.
It's pretty much all-or-nothing now: the GUC does not give you any sort
of useful control over *which* joins are reorderable.
regards, tom lane
В списке pgsql-hackers по дате отправления: