Re: Fix bug of clearing of waitStart in ProcWakeup()

From: ji xu <thanksgreed(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix bug of clearing of waitStart in ProcWakeup()
Date: 2026-02-24 07:31:06
Message-ID: CANWi6YNc+qC7O086svzf1jO=udJNA8+aa0gqp2BS7tyKB7dLaA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> 于2026年2月24日周二 14:29写道:

> Hi,
>
> I just noticed this while reviewing patch [1]. It looks like this is
> caused by a simple typo.
>
> In ProcWakeup():
> ```
> PGPROC *
> ProcWakeup(PGPROC *proc, ProcWaitStatus waitStatus)
> {
> PGPROC *retProc;
>
> /* Proc should be sleeping ... */
> if (proc->links.prev == NULL ||
> proc->links.next == NULL)
> return NULL;
> Assert(proc->waitStatus == PROC_WAIT_STATUS_WAITING);
>
> /* Save next process before we zap the list link */
> retProc = (PGPROC *) proc->links.next;
>
> /* Remove process from wait queue */
> SHMQueueDelete(&(proc->links));
> (proc->waitLock->waitProcs.size)--;
>
> /* Clean up process' state and pass it the ok/fail signal */
> proc->waitLock = NULL;
> proc->waitProcLock = NULL;
> proc->waitStatus = waitStatus;
> pg_atomic_write_u64(&MyProc->waitStart, 0); <== Here, it should
> operate on proc
>
> /* And awaken it */
> SetLatch(&proc->procLatch);
>
> return retProc;
> }
> ```
>
> Since this function is clearly operating on the parameter proc, the only
> statement that touches MyProc looks suspicious. It should reset
> proc->waitStart, not MyProc->waitStart.
>
> As written, it will incorrectly clear the caller’s waitStart instead of
> the awakened backend’s, potentially leaving a stale waitStart value in the
> target PGPROC.
>
> [1]
> https://postgr.es/m/CAHGQGwGw4LhNwOGQT3nbw3uWy8gL94_MB4T39Wfr4_Vgopuovg@mail.gmail.com
>
> Best regards,
> --
> Chao Li (Evan)
> HighGo Software Co., Ltd.
> https://www.highgo.com/
>
>
>
>
>
>
>
Hi ,

The fix looks correct to me. I applied it locally and build and "make
check" passed from my side.

Regards,
ji xu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-02-24 08:00:00 Re: Refactor recovery conflict signaling a little
Previous Message Chao Li 2026-02-24 07:25:04 Re: add assertion for palloc in signal handlers