Re: [HACKERS] The case for removing replacement selection sort - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] The case for removing replacement selection sort
Date
Msg-id CAH2-Wzncu0YiQRoFoLf_zo6iZT6a0WwmGE3FYQCw4C6grfj8UQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] The case for removing replacement selection sort  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Wed, Sep 27, 2017 at 12:06 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> I think we should remove the replacement_sort_tuples GUC, and kill
>> replacement selection entirely. There is no need to do this for
>> Postgres 10. I don't feel very strongly about it. It just doesn't make
>> sense to continue to support replacement selection.
>
> Forgive me if I missed the explanation, but how will we handle bounded sorts?

No change there at all. If anything they will probably be slightly
faster, because the heap management routines don't have to work with a
special heap comparator that compares run number, but only when
replacement selection is in use.

-- 
Peter Geoghegan


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Surjective functional indexes
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] A design for amcheck heapam verification