On Fri, Apr 8, 2016 at 10:09 PM, Peter Geoghegan <p...@heroku.com> wrote:
> On Wed, Mar 30, 2016 at 8:02 AM, Alexander Korotkov > <aekorot...@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. > Patch was rebased to current master. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
partial-sort-basic-9.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
