From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Anj Adu <fotographs(at)gmail(dot)com> |
Cc: | Andy Colson <andy(at)squeakycode(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: slow query performance |
Date: | 2010-06-10 02:12:41 |
Message-ID: | AANLkTilD4kN8bc7I3XauXEaryvsEZ-mXebx5yk71Vv6r@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Jun 3, 2010 at 4:37 PM, Anj Adu <fotographs(at)gmail(dot)com> wrote:
> Link to plan
>
> http://explain.depesz.com/s/kHa
Your problem is likely related to the line that's showing up in red:
Index Scan using dev4_act_dy_fact_2010_05_t3_thedate on
dev4_act_dy_fact_2010_05_t3 a (cost=0.00..94041.89 rows=204276
width=60) (actual time=164533.725..164533.725 rows=0 loops=1)
* Index Cond: ((thedate >= '2010-05-22 00:00:00'::timestamp
without time area) AND (thedate <= '2010-05-22 00:00:00'::timestamp
without time area))
* Filter: (node_id = $0)
This index scan is estimated to return 204,276 rows and actually
returned zero... it might work better to rewrite this part of the
query as a join, if you can:
node_id=(select node_id from dev4_act_node where node='10.90.100.2')
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-10 02:55:20 | Re: slow query performance |
Previous Message | Robert Haas | 2010-06-10 01:51:39 | Re: Large (almost 50%!) performance drop after upgrading to 8.4.4? |