Re: POC: GROUP BY optimization

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: POC: GROUP BY optimization
Date: 2018-06-29 13:11:37
Message-ID: 1913e082-0d8d-5eb8-c8ca-053af828076a@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/28/2018 06:52 PM, Teodor Sigaev wrote:
>> I'm afraid that's a misunderstanding - my objections did not really go
>> away. I'm just saying my claim that we're not messing with order of
>> grouping keys is not entirely accurate, because we do that in one
>> particular case.
>>
>> I still think we need to be careful when introducing new optimizations
>> in this area - reordering the grouping keys by ndistinct, ORDER BY or
>> whatever. In particular I don't think we should commit these patches
>> that may quite easily cause regressions, and then hope some hypothetical
>> future patch fixes the costing. Those objections still stand.
>
> Pls, have a look at https://commitfest.postgresql.org/18/1706/
> I tried to attack the cost_sort() issues and hope on that basis we can
> solve problems with 0002 patch and improve incremental sort patch.
>

OK, will do. Thanks for working on this!

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2018-06-29 13:20:02 Re: Code of Conduct committee: call for volunteers
Previous Message Tomas Vondra 2018-06-29 13:05:32 Re: Remove mention in docs that foreign keys on partitioned tables are not supported