Re: Adding an additional join causes very different/slow query plan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mon, Dec 16, 2013 at 4:14 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Joe Van Dyk <joe@xxxxxxxxx> 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.

Is there a way to measure the planning time? It's not reported in 'explain analyze' or 'explain analyze verbose', right?

Joe

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux