From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: no partition pruning when partitioning using array type |
Date: | 2018-07-11 00:41:46 |
Message-ID: | bbd34ef6-5b90-2142-4584-eea43b318b81@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018/07/11 4:48, Alvaro Herrera wrote:
> On 2018-Jul-10, Alvaro Herrera wrote:
>
>> alvherre=# explain update p set a = a || a where a = '{1}';
>> QUERY PLAN
>> ──────────────────────────────────────────────────────────
>> Update on p (cost=0.00..54.03 rows=14 width=38)
>> Update on p1
>> Update on p2
>> -> Seq Scan on p1 (cost=0.00..27.02 rows=7 width=38)
>> Filter: (a = '{1}'::integer[])
>> -> Seq Scan on p2 (cost=0.00..27.02 rows=7 width=38)
>> Filter: (a = '{1}'::integer[])
>> (7 filas)
>>
>> Because UPDATE uses the predtest.c prune code, not partprune. So it's
>> not just some ruleutils beautification.
>
> I added this test, modified some comments, and pushed.
>
> Thanks for the patch.
Thank you for committing.
Regards,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2018-07-11 01:03:44 | RE: How can we submit code patches that implement our (pending) patents? |
Previous Message | Michael Paquier | 2018-07-11 00:37:54 | Re: _isnan() on Windows |