pgsql: Replace polyphase merge algorithm with a simple balanced k-way m - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Replace polyphase merge algorithm with a simple balanced k-way m
Date
Msg-id E1mcRXp-0000e9-0Y@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Replace polyphase merge algorithm with a simple balanced k-way m  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-committers
Replace polyphase merge algorithm with a simple balanced k-way merge.

The advantage of polyphase merge is that it can reuse the input tapes as
output tapes efficiently, but that is irrelevant on modern hardware, when
we can easily emulate any number of tape drives. The number of input tapes
we can/should use during merging is limited by work_mem, but output tapes
that we are not currently writing to only cost a little bit of memory, so
there is no need to skimp on them.

This makes sorts that need multiple merge passes faster.

Discussion: https://www.postgresql.org/message-id/420a0ec7-602c-d406-1e75-1ef7ddc58d83%40iki.fi
Reviewed-by: Peter Geoghegan, Zhihong Yu, John Naylor

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/65014000b351d5725eb00d133416ab1b4f8245b1

Modified Files
--------------
src/backend/utils/sort/tuplesort.c | 662 ++++++++++++++++---------------------
1 file changed, 293 insertions(+), 369 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Refactor LogicalTapeSet/LogicalTape interface.
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix format modifier used in elog.