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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Tomas Vondra <tv(at)fuzzy(dot)cz>
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream
Date: 2026-03-03 20:07:17
Message-ID: CAAKRu_bAfvo84NKPRT--wUdV5YtHaYqo1=-QiKkiaDSjDPB9hg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 3, 2026 at 2:47 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> Some ideas I had that I didn't include in v4-0003 because its Andres
> patch and is subjective:

I was just looking at another patch and realized test_read_stream.c
exists. I wonder if any of the code this patch set adds to test_aio.c
should be there? On the one hand the foreign IO test is testing AIO
behavior and not really read stream behavior even though it invokes
the read stream. So maybe it doesn't really belong in
0004_read_stream.pl? The repeated blocks test is more of a read
stream test. Anyway, just a thought I had.

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-03 20:31:25 Re: enhance wraparound warnings
Previous Message Álvaro Herrera 2026-03-03 19:48:45 Re: UBSAN crash in EventTriggerCollectAlterTSConfig (memcpy with NULL src)