Re: Problem with default partition pruning

From: yuzuko <yuzukohosoya(at)gmail(dot)com>
To: Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Problem with default partition pruning
Date: 2019-03-05 09:13:32
Message-ID: CAKkQ50-AR185kjHyMgr6-V1GVrrEv+XHxE_UC_fiRa3GvMa5rw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Ibrar,

On Tue, Mar 5, 2019 at 2:37 AM Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> wrote:
>
> Hi Yuzuko Hosoya,
>
> Ignore my last message, I think this is also a legitimate scan on default partition.
>
Oh, I got it. Thanks a lot.

>
> On Mon, Mar 4, 2019 at 10:29 PM Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> wrote:
>>
>> Hi
>>
>> Patch work fine to me, but I have one test case where default partition still scanned.
>>
>> postgres=# explain select * from test1 where (id < 10) and true;
>> QUERY PLAN
>> -------------------------------------------------------------------
>> Append (cost=0.00..55.98 rows=846 width=36)
>> -> Seq Scan on test1_1 (cost=0.00..25.88 rows=423 width=36)
>> Filter: (id < 10)
>> -> Seq Scan on test1_def (cost=0.00..25.88 rows=423 width=36)
>> Filter: (id < 10)
>> (5 rows)
>
>
>
> --
> Ibrar Ahmed

--
Best regards,
Yuzuko Hosoya
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matwey V. Kornilov 2019-03-05 09:16:27 Re: [PATCH 0/3] Introduce spgist quadtree @<(point,circle) operator
Previous Message David Steele 2019-03-05 09:10:55 Re: NOT IN subquery optimization