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

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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-30 19:00:00
Message-ID: 9ce8f5d8-8ab2-4aa2-b062-c5d74161069c@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Andres,

28.03.2026 02:01, Andres Freund wrote:
> Pushed.

As copperhead showed [1], tests added in 020c02bd9 fail when postgres is
built without --enable-cassert. I've reproduced the failure locally with:

./configure -q --enable-debug --enable-tap-tests && make -s -j12 &&
make -s check -C src/test/modules/test_aio/

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2026-03-29%2022%3A01%3A20

Best regards,
Alexander

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-03-30 19:14:30 Re: [BUG] Excessive memory usage with update on STORED generated columns.
Previous Message Andrew Dunstan 2026-03-30 18:52:54 Re: [PATCH] Add support for INSERT ... SET syntax