Re: POC: GROUP BY optimization - Mailing list pgsql-hackers

From Andrey Lepikhov
Subject Re: POC: GROUP BY optimization
Date
Msg-id 7256159a-bb83-7ef3-c9c9-b2188a29aaf8@postgrespro.ru
Whole thread Raw
In response to Re: POC: GROUP BY optimization  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: POC: GROUP BY optimization  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-hackers
On 3/10/2022 21:56, Tom Lane wrote:
 > Revert "Optimize order of GROUP BY keys".
 >
 > This reverts commit db0d67db2401eb6238ccc04c6407a4fd4f985832 and
 > several follow-on fixes.
 > ...
 > Since we're hard up against the release deadline for v15, let's
 > revert these changes for now.  We can always try again later.

It may be time to restart the project. As a first step, I rebased the 
patch on the current master. It wasn't trivial because of some latest 
optimizations (a29eab, 1349d27 and 8d83a5d).
Now, Let's repeat the review and rewrite the current path according to 
the reasons uttered in the revert commit.

-- 
regards,
Andrey Lepikhov
Postgres Professional

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: ObjectIdGetDatum() missing from SearchSysCache*() callers
Next
From: Joan
Date:
Subject: Re: There should be a way to use the force flag when restoring databases