Remove replacement selection sort.

At the time replacement_sort_tuples was introduced, there were still
cases where replacement selection sort noticeably outperformed using
quicksort even for the first run.  However, those cases seem to have
evaporated as a result of further improvements made since that time
(and perhaps also advances in CPU technology).  So remove replacement
selection and the controlling GUC entirely.  This makes tuplesort.c
noticeably simpler and probably paves the way for further
optimizations someone might want to do later.

Peter Geoghegan, with review and testing by Tomas Vondra and me.

Discussion: 
https://postgr.es/m/cah2-wzmmnjg_k0r9nqywmq3zjyjjk+hcbizynghay-zyjs6...@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/8b304b8b72b0a60f1968d39f01cf817c8df863ec

Modified Files
--------------
doc/src/sgml/config.sgml                      |  39 ---
doc/src/sgml/release-9.6.sgml                 |   2 +-
src/backend/utils/init/globals.c              |   1 -
src/backend/utils/misc/guc.c                  |  10 -
src/backend/utils/misc/postgresql.conf.sample |   1 -
src/backend/utils/sort/tuplesort.c            | 415 +++-----------------------
src/include/miscadmin.h                       |   1 -
src/test/regress/expected/cluster.out         |  17 +-
src/test/regress/sql/cluster.sql              |  14 +-
9 files changed, 52 insertions(+), 448 deletions(-)


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

Reply via email to