Getting rid of nested loop - Mailing list pgsql-performance

From Rod Taylor
Subject Getting rid of nested loop
Date
Msg-id 1096073834.40463.41.camel@jester
Whole thread Raw
List pgsql-performance
I set nested_loop = off, which is why I have the high cost.

@ is a postgis operator between 2 geomotries (both polygons). It's the @
operator which is expensive. Is there a way to force a cheaper way of
doing that join?

         ->  Nested Loop  (cost=100001905.94..100001906.08 rows=1
width=68) (actual time=1739.368..17047.422 rows=100 loops=1)
               Join Filter: ((COALESCE("outer".geom, "outer".geom) @
COALESCE("inner".geom, "inner".geom)) AND ("outer".region_id <>
"inner".region_id))



pgsql-performance by date:

Previous
From: Qing Zhao
Date:
Subject: performance of PostgreSQL on 64 bit MAC OS X G5!
Next
From: Gaetano Mendola
Date:
Subject: Re: Caching of Queries