Re: Slow join using network address function

From: Markus Bertheau <twanger(at)bluetwanger(dot)de>
To: josh(at)agliodbs(dot)com
Cc: Eric Jain <Eric(dot)Jain(at)isb-sib(dot)ch>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Slow join using network address function
Date: 2004-02-24 01:23:27
Message-ID: 1077585807.2258.0.camel@yarrow.bertheau.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Пнд, 2004-02-23 at 12:04 -0800, Josh Berkus wrote:
> Eric,
>
> > Nested Loop
> > (cost=189.00..27359887.76 rows=607947200 width=22)
> > Join Filter: ("outer".address <<= "inner".address)
> > -> Seq Scan on clients c
> > (cost=0.00..2074.76 rows=102176 width=11)
> > -> Materialize
> > (cost=189.00..308.00 rows=11900 width=11)
> > -> Seq Scan on clients_commercial cc
> > (cost=0.00..189.00 rows=11900 width=11)
>
> To help you, we need EXPLAIN ANALYZE, not just EXPLAIN. Thanks!

He said he cancelled the query.

--
Markus Bertheau <twanger(at)bluetwanger(dot)de>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ed L. 2004-02-24 02:10:57 [PERFORMANCE] slow small delete on large table
Previous Message Sean Shanny 2004-02-24 00:54:07 Re: General performance questions about postgres on Apple