Luke,
> We (GP) have implemented
> something we call "Adaptive Nested Loop" to replace a nested loop +
> index scan with a hash join when the selectivity estimates are off in
> order to improve this behavior. We also run with a
> "random_page_cost=100" because we generally run on machines with fast
> sequential I/O.
So, when is this getting contributed? ;-)
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
