Search Postgresql Archives

Re: Very bad plan when using VIEW and IN (SELECT...*)

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

 



"Carlo Stonebanks" <stonec.register@xxxxxxxxxxxx> writes:
>>> Having said that, modern versions of the planner seem to deal reasonably
>>> well with this situation as long as they're being asked to push the
>>> condition through a UNION ALL.  Do you really need a UNION in that view?

> This is PG v 8.3 - do you mean "modern" compared to that?

When I was testing it yesterday it seemed that versions back to 8.2
generated acceptable plans, but the results might depend on details you
didn't show us.  Try it and see.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[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