Skip site navigation (1) Skip section navigation (2)

Re: Postgres not using indexes

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Lawrence Cohan <LCohan(at)web(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Postgres not using indexes
Date: 2011-04-01 01:56:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, Mar 31, 2011 at 11:33 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Greg Stark <gsstark(at)mit(dot)edu> wrote:
>> your query does require reading all the data.
> Huh?  It requires reading all the data from at least *one* of the
> tables.

The query he posted a plan for was:

EXPLAIN ANALYZE select from order_items oi inner join
clients_orders co on oi.order_id =;

And the plan for it looks like it's optimal to me:

'Hash Join  (cost=780.55..1908023.16 rows=1027457 width=4) (actual
time=63.506..85607.003 rows=33768 loops=1)'
'  Hash Cond: (oi.order_id ='
'  ->  Seq Scan on order_items oi  (cost=0.00..1558536.52
rows=33843152 width=8) (actual time=0.005..69718.563 rows=33909137
'  ->  Hash  (cost=480.80..480.80 rows=23980 width=4) (actual
time=13.072..13.072 rows=23980 loops=1)'
'        Buckets: 4096  Batches: 1  Memory Usage: 844kB'
'        ->  Seq Scan on clients_orders co  (cost=0.00..480.80
rows=23980 width=4) (actual time=0.006..6.570 rows=23980 loops=1)'
'Total runtime: 85613.391 ms'


In response to


pgsql-bugs by date

Next:From: Craig RingerDate: 2011-04-01 03:49:20
Subject: Re: BUG #5939: About bytea
Previous:From: Raphael GiovaniniDate: 2011-04-01 01:50:34
Subject: default password for user postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group