Getting rid of nested loop

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Getting rid of nested loop
Date: 2004-09-25 00:57:15
Message-ID: 1096073834.40463.41.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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))

Browse pgsql-performance by date

  From Date Subject
Next Message Gaetano Mendola 2004-09-25 16:58:09 Re: Caching of Queries
Previous Message Qing Zhao 2004-09-24 19:23:03 performance of PostgreSQL on 64 bit MAC OS X G5!