Search Postgresql Archives

Re: full outer join performance

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

 



On Tue, 2005-09-13 at 13:28, Ben wrote:
> Hrm, as I understand that page, there's not much that can be done about 
> the join order for outer joins. At least, not when there's on 3 tables 
> and 1 outer join involved. Am I missing something?

You might be able to do some kind of thing like:

select * from (
	select * from table1 <whereclausehere>) as a
	) left join (
	select * from table2 <whereclausehere) as b
on 	(a.somefield=b.somefield2)
where	<anotherwhereclause)

or something.

Tom, would that help the planner make better choices for this kind of
query?

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[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