I suspect that, since the matched hid's probably aren't sequential,
many of those ~500 product_price_offer_history rows will be far apart
on disk.
OMG I was a fool! I'll CLUSTER on a different index and it will be fast,
I'm sure.
Thanks!
L
--
Sent via pgsql-performance mailing list (pgs
2011/3/23 Laszlo Nagy :
> "GroupAggregate (cost=5553554.25..5644888.17 rows=2283348 width=50)"
> " -> Sort (cost=5553554.25..5559262.62 rows=2283348 width=50)"
> " Sort Key: pph.hid, ppoh.merchantid, pph.hdate"
> " -> Nested Loop (cost=0.00..5312401.66 rows=2283348 width=50)"
>