Re: tuple radix sort

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: tuple radix sort
Date: 2025-10-30 03:45:32
Message-ID: 98232211-F000-45E6-AEE7-718834DDE277@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Oct 30, 2025, at 11:40, John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> On Thu, Oct 30, 2025 at 8:56 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
>> I changed work_men to 1GB and reran the test. As the high cardinality data are still there, so I first reran with data:
>
>> With radix_sort on and off, execution time are almost the same.
>
> Are you by chance running with asserts on? It's happened before, so I
> have to make sure. That makes a big difference here because I disabled
> diversion thresholds in assert builds so that regression tests (few
> cases with large inputs) cover the paths I want, in addition to my
> running a standalone stress test.
>

Yes, assert is always enabled in my sandbox. I can disable assert and rerun the test later.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2025-10-30 03:55:29 Re: [PING] fallocate() causes btrfs to never compress postgresql files
Previous Message Fujii Masao 2025-10-30 03:42:27 Re: display hot standby state in psql prompt