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-20 11:32:00
Message-ID: 287d6970.7233.1a01ef13a3c.Coremail.jiezhilove@126.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2026-08-20 18:56:32, "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com> wrote:
>One general place is PgAioHandle, I put wait_event_info into
>PgAioHandle but now its size is increased from 144 to 152. I couldn't
>find a better place, do you have any suggestions?

Hi,
I've reviewed your patch.
I noticed that under the default io_method=worker,
asynchronous reads from mdreadv still report AIO_IO_COMPLETION when the backend gets blocked.
The caller‑supplied wait_event_info is still being ignored.
Is this a problem?

Best regards,

--

Yilin Zhang

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Kukushkin 2026-08-20 11:40:03 Re: pg_dump: assert failure sorting casts/transforms
Previous Message Yuhang Qiu 2026-08-20 11:13:22 Re: Changing shared_buffers without restart