| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Should from_collapse be switched off? (queries 10 times faster) |
| Date: | 2018-03-23 14:14:19 |
| Message-ID: | 18405.1521814459@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Peter wrote:
>> I could not find any documentation or evaluation that would say
>> that from_collapse can have detrimental effects. Even less, which
>> type of queries may suffer from that.
> https://www.postgresql.org/docs/current/static/explicit-joins.html
> states towards the end of the page that the search tree grows
> exponentially with the number of relations, and from_collapse_limit
> can be set to control that.
It's conceivable that the OP's problem is actually planning time
(if the query joins sufficiently many tables) and that restricting
the cost of the join plan search is really what he needs to do.
Lacking any further information about the problem, we can't say.
We can, however, point to
https://wiki.postgresql.org/wiki/Slow_Query_Questions
concerning how to ask this type of question effectively.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter | 2018-03-23 14:30:21 | Re: Should from_collapse be switched off? (queries 10 times faster) |
| Previous Message | Laurenz Albe | 2018-03-23 11:41:35 | Re: Should from_collapse be switched off? (queries 10 times faster) |