pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Getting rid of nested loop
Date: Fri, 24 Sep 2004 20:57:15 -0400
Message-ID: <1096073834.40463.41.camel@jester> (raw)

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))





Message-ID: <1096073834.40463.41.camel@jester>
Permalink:  ../1096073834.40463.41.camel@jester/
Also on:    postgresql.org/message-id/1096073834.40463.41.camel@jester

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pg@rbt.ca
  Subject: Re: Getting rid of nested loop
  In-Reply-To: <1096073834.40463.41.camel@jester>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox