Re: [PATCH] LockAcquireExtended improvement

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jingxian Li <aqktjcm(at)qq(dot)com>
Cc: andres <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] LockAcquireExtended improvement
Date: 2024-03-14 13:15:56
Message-ID: CA+TgmoYc56fSB-CcO3dJiwEAT8DP6ybmQS0+xb3ucWVMXjTXHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 12, 2024 at 9:33 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Mar 11, 2024 at 11:11 PM Jingxian Li <aqktjcm(at)qq(dot)com> wrote:
> > Your version changes less code than mine by pushing the nowait flag down
> > into ProcSleep(). This looks fine in general, except for a little advice,
> > which I don't think there is necessary to add 'waiting' suffix to the
> > process name in function WaitOnLock with dontwait being true, as follows:
>
> That could be done, but in my opinion it's not necessary. The waiting
> suffix will appear only very briefly, and probably only in relatively
> rare cases. It doesn't seem worth adding code to avoid it.

Seeing no further discussion, I have committed my version of this
patch, with your test case.

Thanks for pursuing this improvement!

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-03-14 13:20:56 Re: BitmapHeapScan streaming read user and prelim refactoring
Previous Message Jelte Fennema-Nio 2024-03-14 13:03:19 Re: Flushing large data immediately in pqcomm