Re: [PERFORM] Spatial join insists on sequential scan of larger table

2004-04-02 Thread Tom Lane
Clive Page <[EMAIL PROTECTED]> writes: > This executes, it need hardly be said, a whole lot faster. Could we see EXPLAIN ANALYZE output? The estimated costs for the two cases are nearly the same, which says to me that there's something wrong with the cost model for r-tree lookups, but I don't kno

[PERFORM] Spatial join insists on sequential scan of larger table

2004-04-02 Thread Clive Page
I am trying to do a spatial join between two tables each of which has a column of type BOX called ERRBOX, with R-TREE indices created on both. The smaller table, xmm1, has 56,711 rows, the larger one, twomass, has 177,757,299 rows. The most efficient way to join these is to do a sequential s