On Wed, Mar 30, 2016 at 8:02 AM, Alexander Korotkov
<aekorotkov@gmail.com> wrote:
> Hmm... I'm not completely agree with that. In typical usage partial sort
> should definitely use quicksort. However, fallback to other sort methods is
> very useful. Decision of partial sort usage is made by planner. But
> planner makes mistakes. For example, our HashAggregate is purely in-memory.
> In the case of planner mistake it causes OOM. I met such situation in
> production and not once. This is why I'd like partial sort to have graceful
> degradation for such cases.
I think that this should be moved to the next CF, unless a committer
wants to pick it up today.
--
Peter Geoghegan
