Search Postgresql Archives

Re: Bad Estimate for complex query with JOINS on subselects and OR in where conditions

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

 



Peter Grman <peter.grman@xxxxxxxxx> writes:
> our ORM with tenant separation enabled is creating the following query:

Ugh.

By my count there are nine joined tables in that query, which means
you're hitting the default join_collapse_limit.  Increasing that
setting might improve matters somewhat, though it won't fix the
bad rowcount estimate per se.

			regards, tom lane





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux