Re: Don't synchronously wait for already-in-progress IO in read stream

On Thu, Sep 11, 2025 at 5:46 PM Andres Freund <andres@anarazel.de> wrote:
> The problem leading to that is that we are currently synchronously waiting for
> IO on a buffer when AsyncReadBuffers() encounters a buffer already undergoing
> IO. If a block is read twice, that means we won't actually have enough IOs in
> flight to have good performance. What's worse, currently the wait is not
> attributed to IO wait (since we're waiting in WaitIO, rather than waiting for
> IO).

This patch no longer cleanly applies. Can you post a new version?

Thanks
--
Peter Geoghegan