Request a Demo
Home   >   mailing lists

Re: Fix incorrect buffer lock description in pg_visibility comment - Mailing list pgsql-hackers

From Chao Li
Subject Re: Fix incorrect buffer lock description in pg_visibility comment
Date
Msg-id 1F660F7C-347D-4229-905D-44414B855983@gmail.com
Whole thread Raw
In response to Re: Fix incorrect buffer lock description in pg_visibility comment  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Fix incorrect buffer lock description in pg_visibility comment
List pgsql-hackers
Tree view 

> On Jan 6, 2026, at 02:41, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> I find that "shared locked" sounds unnatural to me. How about
> rephrasing to "... we're holding the buffer locked in shared mode”?

Hi Masahiko-san,

Thanks for taking care of this patch. Yeah, I agree “shared locked” is not good, at least it should be “shared-ly
locked”.So, Your version, “locked in shared mode” is better. 

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Should we say "wal_level = logical" instead of "wal_level >= logical"
Next
From: Niyaz Hazigaleyev
Date:
Subject: Re: [PATCH] meson: Update meson to enable building postgres as a subproject