|From:||Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>|
|To:||Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>|
|Cc:||PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Partition-wise aggregation/grouping|
|Views:||Raw Message | Whole Thread | Download mbox|
On Tue, Sep 12, 2017 at 6:21 PM, Jeevan Chalke <
> On Tue, Sep 12, 2017 at 3:24 PM, Rajkumar Raghuwanshi <
> rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com> wrote:
>> Hi Jeevan,
>> I have started testing partition-wise-aggregate and got one observation,
>> please take a look.
>> with the v2 patch, here if I change target list order, query is not
>> picking full partition-wise-aggregate.
> Thanks Rajkumar for reporting this.
> I am looking into this issue and will post updated patch with the fix.
Logic for checking whether partition keys lead group by keys needs to be
updated here. The group by expressions can appear in any order without
affecting the final result. And thus, the need for partition keys should
be leading the group by keys to have full aggregation is not mandatory.
Instead we must ensure that the partition keys are part of the group by
keys to compute full aggregation on a partition.
Attached, revised patch-set with above fix.
Also, in test-cases, I have removed DROP/ANALYZE commands on child
relations and also removed VERBOSE from the EXPLAIN.
Partition-wise Join patch-set version: v32
Principal Software Engineer, Product Development
The Enterprise PostgreSQL Company
|Next Message||Rushabh Lathia||2017-09-18 07:16:24||Re: GatherMerge misses to push target list|
|Previous Message||Michael Paquier||2017-09-18 06:33:39||Re: pg_control_recovery() return value when not in recovery|