Postgres Pro
Downloads
Home   >   mailing lists

Re: Spatial join insists on sequential scan of larger table - Mailing list pgsql-performance

From Tom Lane
Subject Re: Spatial join insists on sequential scan of larger table
Date
Msg-id 27943.1080920786@sss.pgh.pa.us
Whole thread Raw
In response to Spatial join insists on sequential scan of larger table  (Clive Page <cgp@star.le.ac.uk>)
Responses Re: Spatial join insists on sequential scan of larger  (Clive Page <cgp@star.le.ac.uk>)
Re: Spatial join insists on sequential scan of larger  (Clive Page <cgp@star.le.ac.uk>)
List pgsql-performance
Tree view 
Clive Page <cgp@star.le.ac.uk> 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 know what it is.

            regards, tom lane

pgsql-performance by date:

Previous
From: Clive Page
Date:
Subject: Spatial join insists on sequential scan of larger table
Next
From: Bruno Wolff III
Date:
Subject: Re: single index on more than two coulumns a bad thing?