ng it on top of Hosoya's last 2 patches, It corrects the
different cases we found so far.
I will keep on testing next week.
Cordialement,
Thibaut
Le 22/03/2019 à 07:38, Amit Langote a écrit :
> Hosoya-san,
>
> On 2019/03/22 15:02, Yuzuko Hosoya wrote:
>> I understood Amit's proposal. But I think the issue Thibaut reported would
>> occur regardless of whether clauses have OR clauses or not as follows.
>&g
Le 20/03/2019 à 10:06, Amit Langote a écrit :
> Hi Thibaut,
>
> On 2019/03/19 23:58, Thibaut Madelaine wrote:
>> I kept on testing with sub-partitioning.
> Thanks.
>
>> I found a case, using 2 default partitions, where a default partition is
>> not pruned:
>&g
=0.00..35.40 rows=13 width=36)
>>> Filter: (((id > 0) AND (id < 30)) OR ((id > 220) AND (id <
>>> 230)))
>>> (5 rows)
>>>
>>> v2 patch attached.
>>> Could you please check it again?
>> I think the updated patch breaks t
-
Append (cost=0.00..29.08 rows=6 width=36)
-> Seq Scan on test1_3_1 (cost=0.00..29.05 rows=6 width=36)
Filter: ((id > 220) AND (id < 230))
(3 rows)
# explain select * from test1
where (id > 0 and id < 30) or (id > 220 and id < 230);
QUERY PLAN
---
Append (cost=0.00..106.40 rows=39 width=36)
-> Seq Scan on test1_1 (cost=0.00..35.40 rows=13 width=36)
Filter: (((id > 0) AND (id < 30)) OR ((id > 220) AND (id < 230)))
-> Seq Scan on test1_3_1 (cost=0.00..35.40 rows=13 width=36)
Filter: (((id > 0) AND (id < 30)) OR ((id > 220) AND (id < 230)))
-> Seq Scan on test1_3_2 (cost=0.00..35.40 rows=13 width=36)
Filter: (((id > 0) AND (id < 30)) OR ((id > 220) AND (id < 230)))
(7 rows)
-
Partition pruning is functioning when only the sub-partition is
required. When both the partition and the sub-partition is required,
there is no pruning on the sub-partition.
Cordialement,
--
Thibaut Madelaine
Dalibo
