| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Chengpeng Yan <chengpeng_yan(at)outlook(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: tuple radix sort |
| Date: | 2025-11-26 06:55:30 |
| Message-ID: | CANWCAZagi+aTW0AapZ09ZXr0-Di99dq8o426d6agmR8FRtqD_g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 26, 2025 at 1:52 PM John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
> This made me think of something tangential: v4's common prefix
> skipping doesn't take into account that the upper 4 bytes can't
> matter. With a mix of positive and negative integers, I think it will
> do the radix sort on all 8 bytes of "datum1".
I accidentally edited out some context: The above is referring to SQL
"int" sort keys, i.e. 32-bit signed integers.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arseniy Mukhin | 2025-11-26 07:00:31 | Re: [PATCH] Avoid pallocs in async.c's "critical section" |
| Previous Message | John Naylor | 2025-11-26 06:52:42 | Re: tuple radix sort |