Postgres Pro
Downloads
Home   >   mailing lists

Re: Adding an additional join causes very different/slow query plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Adding an additional join causes very different/slow query plan
Date
Msg-id 18828.1387239245@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding an additional join causes very different/slow query plan  (Joe Van Dyk <joe@tanga.com>)
Responses Re: Adding an additional join causes very different/slow query plan  (Joe Van Dyk <joe@tanga.com>)
List pgsql-performance
Tree view 
Joe Van Dyk <joe@tanga.com> writes:
> Hm, setting set join_collapse_limit = 9 seemed to fix the problem. Is that
> my best/only option?

Yup, that's what I was just about to suggest.  You might want to use
10 or 12 in case some of your queries are a bit more complex than
this one --- but don't go overboard, or you may find yourself with
unreasonable planning time.

            regards, tom lane

pgsql-performance by date:

Previous
From: Joe Van Dyk
Date:
Subject: Re: Adding an additional join causes very different/slow query plan
Next
From: Joe Van Dyk
Date:
Subject: Re: Adding an additional join causes very different/slow query plan