From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mehdirahbvd(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15102: Performance problem when doing join, index are not used |
Date: | 2018-03-08 15:41:04 |
Message-ID: | 12626.1520523664@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> Here is the query:
> [ select with 11 input tables ]
Perhaps raising join_collapse_limit to 11 or more would let the query
planner find a better plan. Having said that, I see no especially good
reason to think that sort-and-merge isn't a good join type for this query.
Indexes aren't always the answer, especially not when joining large
numbers of rows as you are here.
Another direction to pursue is to raise work_mem to allow the sorts to
proceed more efficiently. Don't go overboard on that, but judicious
increases can help.
Lastly, I see no reason whatever to think this is a bug. You might
have better luck discussing the issue on the pgsql-performance list.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2018-03-08 18:37:29 | When using multiple inheritance, insufficient tests exist for whether a data type change is safe. |
Previous Message | PG Bug reporting form | 2018-03-08 15:10:34 | BUG #15102: Performance problem when doing join, index are not used |