Re: Trivial fix for comment of function table_tuple_lock

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Trivial fix for comment of function table_tuple_lock
Date: 2025-09-22 15:41:41
Message-ID: CAHGQGwEihnukAcLgGA5rVTG8whmYSOCM7LoG8trxMgf04i0w6A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 22, 2025 at 2:54 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
> Hi Fujii-san,
>
> Thank you very much for taking care of this patch.
>
> I just updated the patch, see attached v2. In v2, I removed "tid" from the comment of heap_lock_tuple(), and I found a couple of more occurrences of "relation"=>"rel" in tableam.h.

Thanks for updating the patch! LGTM.

While also checking the comments for table_tuple_delete() and
table_tuple_update(),
I noticed a few other issues. Wouldn’t it be better to fix these together?

* changingPart is listed as an output parameter for table_tuple_delete(),
but it looks like an input.
* slot is listed as an input parameter for table_tuple_update(), but it seems
to be an output.
* The comment for update_indexes in table_tuple_update() is mis-indented.
* Not an issue, but it might be clearer to add a blank line between the input
and output parameter comments in table_tuple_delete() and
table_tuple_update().

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-09-22 15:44:23 Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ?
Previous Message Andres Freund 2025-09-22 15:41:17 Re: waiteventset.c XXX