Re: Why does the number of rows are different in actual and estimated.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: AI Rumman <rummandba(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Why does the number of rows are different in actual and estimated.
Date: 2012-12-13 23:09:42
Message-ID: 50CA6036.6000107@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On 12/13/2012 05:42 PM, Claudio Freire wrote:
> And it looks like it all may be starting to go south here:
>> -> Hash Join (cost=9337.97..18115.71 rows=34489 width=244) (actual time=418.054..1156.453 rows=205420 loops=1)
>> Hash Cond: (customerdetails.customerid = entity.id)

Well, it looks like it's choosing a join order that's quite a bit
different from the way the query is expressed, so the OP might need to
play around with forcing the join order some.

cheers

andrew

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Evgeny Shishkin 2012-12-13 23:13:29 Re: Why does the number of rows are different in actual and estimated.
Previous Message Claudio Freire 2012-12-13 22:42:05 Re: Why does the number of rows are different in actual and estimated.