Re: totally different plan when using partitions

From: Richard Huxton <dev(at)archonet(dot)com>
To: Scara Maccai <m_lists(at)yahoo(dot)it>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: totally different plan when using partitions
Date: 2009-08-14 07:31:29
Message-ID: 4A8512D1.3060404@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scara Maccai wrote:
>> Hmmm ... why is the inner Nested Loop estimated to produce
>> 30120 rows,
>> when the cartesian product of its inputs would only be 285
>> * 14 = 3990
>> rows?
>
> Oh my... didn't notice it!!!

It was doing the same thing here too:
http://explain-analyze.info/query_plans/3807-query-plan-2511
Basically the same location too: nested loop over a seq-scan and an append.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scara Maccai 2009-08-14 07:43:32 Re: totally different plan when using partitions
Previous Message Scara Maccai 2009-08-14 07:12:24 Re: totally different plan when using partitions