Re: sub-select makes query take too long - unusable - Mailing list pgsql-performance

From Sergey Aleynikov
Subject Re: sub-select makes query take too long - unusable
Date
Msg-id a233edb60911220006p7d2c05c1x91c8ca838e8fafad@mail.gmail.com
Whole thread Raw
In response to sub-select makes query take too long - unusable  (Mark Dueck <mark@dueck.bz>)
List pgsql-performance
Hello,

SubPlan 2
    ->  Seq Scan on item_price  (cost=0.00..423.30 rows=1 width=8)
(actual time=1.914..1.914 rows=0 loops=10669)
          Filter: ((item_id = $1) AND (zone_id =
'OUsEaRcAA3jQrg42WHUm8A'::bpchar) AND (price_type = 0) AND
((size_name)::text = ($2)::text))

This means that, for every one of 10669 output rows, DB scanned whole
item_price table, spending 20.4 of 20.8 secs there. Do you have any
indexes there? Especially, on item_id column.

Best regards,
Sergey Aleynikov

pgsql-performance by date:

Previous
From: Mark Dueck
Date:
Subject: sub-select makes query take too long - unusable
Next
From: afancy
Date:
Subject: Re: Performance degrade running on multicore computer