Re: Fix bug of clearing of waitStart in ProcWakeup()
Fujii Masao <masao.fujii@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: ji xu <thanksgreed@gmail.com>, Chao Li <li.evan.chao@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-24T16:37:13Z
Lists: pgsql-hackers
Attachments
- v1-0001-Fix-ProcWakeup-resetting-wrong-waitStart-field.patch (application/octet-stream) patch v1-0001
On Wed, Feb 25, 2026 at 1:12 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> On 2026-Feb-24, ji xu wrote:
>
> > Chao Li <li.evan.chao@gmail.com> 于2026年2月24日周二 14:29写道:
> >
> > > ```
> > > PGPROC *
> > > ProcWakeup(PGPROC *proc, ProcWaitStatus waitStatus)
> > > {
>
> > > pg_atomic_write_u64(&MyProc->waitStart, 0); <== Here, it should
> > > operate on proc
>
> I agree that this looks wrong. AFAICS it comes from 46d6e5f56790.
Yes, it's my mistake...
For the record, patch attached.
Regards,
--
Fujii Masao
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix ProcWakeup() resetting wrong waitStart field.
- 5d2dec77efaf 14.23 landed
- 74ee3e9e7365 15.18 landed
- b993706787d0 16.14 landed
- f72c92a7f945 17.10 landed
- 0d3be0501784 18.4 landed
- 70f470314cb4 19 (unreleased) landed