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

From Simon Riggs
Subject Re: [HACKERS] The case for removing replacement selection sort
Date
Msg-id CANP8+jJ1Br8yd9MaiuyZE75MdpE4L7ndpfg2Z8H59y0BJOfOjQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] The case for removing replacement selection sort  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [HACKERS] The case for removing replacement selection sort  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On 14 July 2017 at 23:20, Peter Geoghegan <pg@bowt.ie> 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?

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
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: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Transactions involving multiple postgres foreign servers
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Surjective functional indexes