Re: aio: Don't silently drop wait_event_info

From: "Yilin Zhang" <jiezhilove(at)126(dot)com>
To: "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com>
Cc: "Andres Freund" <andres(at)anarazel(dot)de>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: aio: Don't silently drop wait_event_info
Date: 2026-08-24 00:54:00
Message-ID: 38ed4ad0.74c.1a031428f37.Coremail.jiezhilove@126.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2026-08-20 20:31:40, "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com> wrote:
>
>I don't think it is a problem, these are two separate wait events,
>reported by two different processes at the same time.
>
>- AIO_IO_COMPLETION is reported when one backend (client backend for
>example) is waiting IO to be done by someone else.
>
>- wait_event_info (WAIT_EVENT_DATA_FILE_READ in this case) is used
>when the actual backend doing the IO is waiting IO to be completed.
>

Hi,
Your description of the parameters looks clear and to the point, thanks. This patch looks good to me.

Best regards,
--
Yilin Zhang

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Kevin Rocker 2026-08-23 23:49:44 Re: [Patch] Make ginInsertCleanup follow vacuum's BufferAccessStrategy