<div dir="ltr">Thanks for the clarifications.<br /><br />Just for curiosity, is there any reason of not having block
nested-loopjoin implementation? Is it rarely useful?<br /><br />As far as I am aware of, in the case of cross product
oftwo tables, block nested-loop join is the most efficient algorithm.<br /><br />Regards,<br /><br />Bramandia R.<br
/><br/><div class="gmail_quote">On Fri, Oct 10, 2008 at 3:30 PM, Gregory Stark <span dir="ltr"><<a
href="mailto:stark@enterprisedb.com">stark@enterprisedb.com</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br
/>Heikki Linnakangas <<a
href="mailto:heikki.linnakangas@enterprisedb.com">heikki.linnakangas@enterprisedb.com</a>>writes:<br /><br />
>>Does postgresql support block nested loop join?<br /> ><br /> > Nope.<br /><br /></div>We do support Hash
Jointhough so I think the only difference is that we can't<br /> use the hash join for cartesian joins.<br /><br />
--<br/> Gregory Stark<br /><div class="Ih2E3d"> EnterpriseDB <a href="http://www.enterprisedb.com"
target="_blank">http://www.enterprisedb.com</a><br/></div> Ask me about EnterpriseDB's PostGIS support!<br
/></blockquote></div><br/></div>
