Re: Nested loops overpriced

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Daniel Cristian Cruz" <danielcristian(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Nested loops overpriced
Date: 2007-05-09 14:34:00
Message-ID: 87sla6gj6v.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


"Daniel Cristian Cruz" <danielcristian(at)gmail(dot)com> writes:

> -> Nested Loop (cost=0.00..13187.94 rows=93 width=4) (actual time=2.622..125.739 rows=50 loops=1)
> -> Seq Scan on u (cost=0.00..2838.80 rows=10289 width=4) (actual time=0.012..9.863 rows=10291 loops=1)
> -> Index Scan using m_pkey on m (cost=0.00..0.80 rows=1 width=7) (actual time=0.009..0.009 rows=0 loops=10291)

That's not discounting the nested loop for cache effect at all!

What is your effective_cache_size for this?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2007-05-09 14:49:08 Re: Apparently useless bitmap scans
Previous Message Gregory Stark 2007-05-09 14:29:58 Re: Poor performance with queries using clause: sth IN (...)