On Sat, Mar 1, 2025 at 1:23 PM Shankaran, Akash
<akash.shankaran@intel.com> wrote:
> Given the same x86-simdsort library is intended to optimize 1) list_sort 2) tuple sort, it didn't make sense to
duplicatethe work to integrate it in pg_vector for list_sort, and then again in postgres for tuple-sort.
Thank you for the context -- the motivation is clear now.
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.
> We're trying to tackle list_sort and tuple_sort in separate patches using the same x86-simdsort library,
with the goal to optimize both. Let us know if this approach is
preferred and if the list_sort patch could be reviewed and any other
tests we should do, or would you rather see tuple_sort benchmarks.
The approach I actually prefer to is to hear about the high-level
architecture first, before being asked to look at code. Tuple sort has
special challenges, so when you're ready to start a new thread for
that, I'll be curious about your findings.
--
John Naylor
Amazon Web Services
