Re: [PATCH] Simple code cleanup in tuplesort.c.

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Xing Guo <higuoxing(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Simple code cleanup in tuplesort.c.
Date: 2023-01-09 09:58:11
Message-ID: CAFBsxsHQVGZPjAW+obBkr1H8CEEi=ussP4s4x2=xw1MMdW-fSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 5, 2023 at 8:18 AM John Naylor <john(dot)naylor(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2023-01-09 10:10:56 Re: POC: Lock updated tuples in tuple_update() and tuple_delete()
Previous Message Aleksander Alekseev 2023-01-09 09:56:12 Re: POC: Lock updated tuples in tuple_update() and tuple_delete()