Re: optimisation? collation "C" sorting for GroupAggregate for alldeterministic collations - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: optimisation? collation "C" sorting for GroupAggregate for alldeterministic collations
Date
Msg-id CADkLM=dhELi6fK8jbPVzfwwnzO729zDzTt=mVax9tJybr0=3_Q@mail.gmail.com
Whole thread Raw
In response to Re: optimisation? collation "C" sorting for GroupAggregate for alldeterministic collations  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
Perhaps this is what you mean by "deterministic", but isn't it
possible for some collations to treat multiple byte sequences as equal
values? And those multiple byte sequences wouldn't necessarily occur
sequentially in C collation, so it wouldn't be possible to work around
that by having the grouping node use one collation but the sorting
node use the C one.

If my memory is incorrect, then this sounds like an intriguing idea.


I could see the value in a hash aggregate on C-collation that then passes itself as a partial aggregate up to another step which applies the collation and then finalizes the aggregation before sorting
 

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: ssl passphrase callback
Next
From: James Coleman
Date:
Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort)