Re: Planner choosing NestedLoop, although it is slower...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Planner choosing NestedLoop, although it is slower...
Date: 2011-07-12 22:39:22
Message-ID: 18737.1310510362@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr> writes:
> On 07/12/2011 10:04 PM, Tom Lane wrote:
>> What you need to look into is why the estimated join size is 9400 rows
>> when the actual join size is zero. Are both tables ANALYZEd? Are you
>> intentionally selecting rows that have no join partners?

> Yes, both tables have been ANALYZEd. What do you mean, intentilnaly
> selecting rows taht have no join partners?

I'm wondering why the actual join size is zero. That seems like a
rather unexpected case for a query like this.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message lars 2011-07-12 23:15:12 Re: UPDATEDs slowing SELECTs in a fully cached database
Previous Message lars 2011-07-12 22:36:20 Re: UPDATEDs slowing SELECTs in a fully cached database