From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | John Naylor <johncnaylorls(at)gmail(dot)com> |
Cc: | "Shankaran, Akash" <akash(dot)shankaran(at)intel(dot)com>, "R, Rakshit" <rakshit(dot)r(at)intel(dot)com>, "Devulapalli, Raghuveer" <raghuveer(dot)devulapalli(at)intel(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, "Giacchino, Luca" <luca(dot)giacchino(at)intel(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Paul, Sourav Kumar" <sourav(dot)kumar(dot)paul(at)intel(dot)com> |
Subject: | Re: SIMD optimization for list_sort |
Date: | 2025-08-06 14:20:24 |
Message-ID: | 202508061420.3gbwyhsqxa65@alvherre.pgsql |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Mar-03, John Naylor wrote:
> I imagine this kind of integration work is messy and difficult, which
> is why I would be reluctant to write something that way if I have a
> choice.
I've marked this commitfest item[1] as Returned with Feedback. Please
feel free to reopen it once you have an updated patch to share. I think
John's reservations on whether to absorb another requisite shared
library is something to strongly consider -- I notice that x86-simd-sort
is not yet packaged by Debian, for instance.
Maybe your needs *are* served better by introducing simd-sort in
pgvector after all? Alternatively: would it be too bad to reimplement
simdsort in C within Postgres rather than using a third party library?
[1] https://commitfest.postgresql.org/patch/5607/
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"If you have nothing to say, maybe you need just the right tool to help you
not say it." (New York Times, about Microsoft PowerPoint)
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-08-06 14:25:53 | Re: analyze-in-stages post upgrade questions |
Previous Message | Tomas Vondra | 2025-08-06 14:12:53 | Re: index prefetching |