t;
>To: PostGIS Users Discussion
>Sent: Monday, April 23, 2012 8:08 PM
>Subject: [postgis-users] help wanted with performance/GIST index question
>
>
>I'm doing some left outer spatial joins using the && operator, which should be
>relatively quick.
>
&g
Try setting:
set enable_seqscan=false;
and then try your explain again. I have run into this before with other
queries and this solved the problem, but I'm sure there is a better way
of dealing with this and I'm not sure what causes it.
-Steve
On 4/23/2012 11:08 PM, pcr...@pcreso.com wrote:
I'm doing some left outer spatial joins using the && operator, which should be
relatively quick.
When I join across 5 tables, the result is fast enough, & explain shows index
scans are being applied to the spatial tables. When I add another table,
explain shows a seq scan is used, despite the
