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 CAFBsxsHQVGZPjAW+obBkr1H8CEEi=ussP4s4x2=xw1MMdW-fSw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Simple code cleanup in tuplesort.c.  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: [PATCH] Simple code cleanup in tuplesort.c.
List pgsql-hackers

On Thu, Jan 5, 2023 at 8:18 AM John Naylor <john.naylor@enterprisedb.com> wrote:
>
> 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.

This has been pushed, thanks. Note that both patches in this thread have the same name. Adding a version number to the name is a good way to distinguish them.

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

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()
Next
From: Alexander Korotkov
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()