Re: [PATCH] LockAcquireExtended improvement
Jingxian Li <aqktjcm@qq.com>
From: "Jingxian Li" <aqktjcm@qq.com>
To: "Will Mortensen" <will@extrahop.com>, robertmhaas <robertmhaas@gmail.com>
Cc: andres <andres@anarazel.de>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2024-05-18T09:10:38Z
Lists: pgsql-hackers
On 2024/5/18 14:38, Will Mortensen wrote: > On Tue, Mar 26, 2024 at 7:14 PM Will Mortensen <will@extrahop.com> wrote: >> This comment on ProcSleep() seems to have the values of dontWait >> backward (double negatives are tricky): >> >> * Result: PROC_WAIT_STATUS_OK if we acquired the lock, >> PROC_WAIT_STATUS_ERROR >> * if not (if dontWait = true, this is a deadlock; if dontWait = false, we >> * would have had to wait). >> >> Also there's a minor typo in a comment in LockAcquireExtended(): >> >> * Check the proclock entry status. If dontWait = true, this is an >> * expected case; otherwise, it will open happen if something in the >> * ipc communication doesn't work correctly. >> >> "open" should be "only". > > Here's a patch fixing those typos. Nice catch! The patch looks good to me. -- Jingxian Li
Commits
-
Fix typo and comments related to the recent no-wait lock improvements
- f7ab71ba0c7b 17.0 landed
-
Allow a no-wait lock acquisition to succeed in more cases.
- 2346df6fc373 17.0 landed