Re: [PATCH] Simple code cleanup in tuplesort.c. - Mailing list pgsql-hackers

From John Naylor
Subject Re: [PATCH] Simple code cleanup in tuplesort.c.
Date
Msg-id CAFBsxsF7bRxHKtu65c2sU5zDUaz_DuBNdgJPTq1PNd+z+bEpZw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Simple code cleanup in tuplesort.c.  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: [PATCH] Simple code cleanup in tuplesort.c.
List pgsql-hackers

On Fri, Sep 16, 2022 at 1:43 PM Richard Guo <guofenglinux@gmail.com> wrote:
>
>
> On Wed, Jul 27, 2022 at 5:10 PM Xing Guo <higuoxing@gmail.com> wrote:
>>
>> The bounded heap sorting status flag is set twice in sort_bounded_heap() and tuplesort_performsort(). This patch helps remove one of them.
>
>  
> Revisiting this patch I think maybe it's better to remove the setting of
> Tuplesort status from tuplesort_performsort() for the TSS_BOUNDED case.
> Thus we keep the heap manipulation routines, make_bounded_heap and
> sort_bounded_heap, consistent in that they update their status
> accordingly inside the function.

The label TSS_BUILDRUNS has a similar style and also the following comment, so I will push this patch with a similar comment added unless someone wants to make a case for doing otherwise.

* Note that mergeruns sets the correct state->status.

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?
Next
From: Matthias van de Meent
Date:
Subject: Re: New strategies for freezing, advancing relfrozenxid early