Re: 回复: An implementation of multi-key sort

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Wang Yao <yaowangm(at)outlook(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: "interma(at)outlook(dot)com" <interma(at)outlook(dot)com>
Subject: Re: 回复: An implementation of multi-key sort
Date: 2024-05-23 12:47:29
Message-ID: 7bbaa17a-0b69-41a9-b48c-e5f461ce809d@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23/05/2024 15:39, Wang Yao wrote:
> No obvious perf regression is expected because PG will follow original
> qsort code path when mksort is disabled. For the case, the only extra
> cost is the check in tuplesort_sort_memtuples() to enter mksort code path.

And what about the case the mksort is enabled, but it's not effective
because all leading keys are different?

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-05-23 13:29:08 Re: Shared detoast Datum proposal
Previous Message Wang Yao 2024-05-23 12:39:06 回复: An implementation of multi-key sort