Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues - Mailing list pgsql-bugs

From Tom Lane
Subject Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues
Date
Msg-id 6999.1186450253@sss.pgh.pa.us
Whole thread Raw
In response to Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues
RE : RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues
List pgsql-bugs
Gregory Stark <stark@enterprisedb.com> writes:
> The structure of your query is a whole series of left outer joins, the result
> of which is then (inner) joined with one more table. The outer joins return a
> whole lot of records but the inner join is only going to match a few of them.

Hmmm ... actually I see 6 tables inside the join-tree and four more
loose in the FROM-clause, ten relations altogether.  Which means the OP
is falling foul of from_collapse_limit, and it's not investigating every
possible join order.  Try setting from_collapse_limit to more than 10.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3504: Some listening sessions never return from writing, problems ensue
Next
From: "Mouhamadou Dia"
Date:
Subject: RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues