Re: Nested loops overpriced - Mailing list pgsql-performance

From Gregory Stark
Subject Re: Nested loops overpriced
Date
Msg-id 87sla6gj6v.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Nested loops overpriced  ("Daniel Cristian Cruz" <danielcristian@gmail.com>)
Responses Re: Nested loops overpriced
List pgsql-performance
"Daniel Cristian Cruz" <danielcristian@gmail.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


pgsql-performance by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Poor performance with queries using clause: sth IN (...)
Next
From: Tom Lane
Date:
Subject: Re: Apparently useless bitmap scans