| From: | David Geier <geidav(dot)pg(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-11-17 15:38:43 |
| Message-ID: | 78befa83-5cf2-4dd9-bf7b-9845df6b19ee@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi John!
On 15.11.2025 03:47, John Naylor wrote:
> On Sat, Nov 15, 2025 at 1:05 AM David Geier <geidav(dot)pg(at)gmail(dot)com> wrote:
>> I understand that you want to make progress with the use case at hand
>> but I feel like we're missing out on a lot of opportunity where the
>> introduced code would also be very beneficial.
>
> The patch is independently beneficial, but is also just a stepping
> stone toward something larger, and I don't yet know exactly how it's
> going to look. Premature abstractions are just going to get in the
> way. I'd be open to hear proposals for possible wider application
> after the dust settles, but that's not going to happen during the PG19
> cycle.
>
That sounds like a good compromise. Let's see what else can profit from
the new sorting code once we've got the tuple sort in.
--
David Geier
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilia Evdokimov | 2025-11-17 15:42:38 | Re: Use merge-based matching for MCVs in eqjoinsel |
| Previous Message | David Geier | 2025-11-17 15:28:23 | Re: Use merge-based matching for MCVs in eqjoinsel |