Re: [PATCH] Use optimized single-datum tuplesort in ExecSort
От | David Rowley |
---|---|
Тема | Re: [PATCH] Use optimized single-datum tuplesort in ExecSort |
Дата | |
Msg-id | CAApHDvpXk2BLz5irPzs8oewsAdDwV_i=VyokOk_54VW0grnm8A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Use optimized single-datum tuplesort in ExecSort (Ronan Dunklau <ronan.dunklau@aiven.io>) |
Ответы |
Re: [PATCH] Use optimized single-datum tuplesort in ExecSort
Re: [PATCH] Use optimized single-datum tuplesort in ExecSort Re: [PATCH] Use optimized single-datum tuplesort in ExecSort |
Список | pgsql-hackers |
On Fri, 16 Jul 2021 at 02:53, Ronan Dunklau <ronan.dunklau@aiven.io> wrote: > Please find attached a v9 just moving the flag setting to ExecInitSort, and my > apologies if I misunderstood your point. I took this and adjusted a few things and ended up with the attached patch. The changes are fairly minor. I made the bracing consistent between both tuplesort_begin calls. I rewrote the comment at the top of ExecSort() to make it more clear about each method used. I also adjusted the comment down at the end of ExecSort that was mentioning something about tuplesort_gettupleslot returning NULL. Your patch didn't touch this, but to me, the comment just looked wrong both before and after the changes. tuplesort_gettupleslot returns false and sets the slot to empty when it runs out of tuples. Anyway, I wrote something there that I think improves that. I feel like this patch is commit-worthy now. However, I'll leave it for a few days, maybe until after the weekend as there's been a fair bit of interest and I imagine someone will have comments to make. David
Вложения
В списке pgsql-hackers по дате отправления: