Re: Non-reproducible AIO failure

From: Andres Freund <andres(at)anarazel(dot)de>
To: Nico Williams <nico(at)cryptonector(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, Alexander Lakhin <exclusion(at)gmail(dot)com>, rmt(at)lists(dot)postgresql(dot)org
Subject: Re: Non-reproducible AIO failure
Date: 2025-07-21 23:19:54
Message-ID: 5fzdhtjdqajptsyg7pisojaqgsc5dpx7wcys5eysezrzubm4eu@2nu64qt5ns4o
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-06-19 10:16:12 -0500, Nico Williams wrote:
> On Thu, Jun 19, 2025 at 05:05:25PM +0200, Daniel Gustafsson wrote:
> > I also dug out an archeologically old MacBook Pro running macOS High Sierra
> > 10.13.6 with an i5 using Apple LLVM version 10.0.0 (clang-1000.10.44.4), and it
> > too fails to reproduce any issue.
>
> It's not going to be reproducible on x86_64 macs. It has to be ARM
> macs.

In addition to various other folks that had reported in, I had various macs,
both real and virtualized, run this test in a loop. For weeks - without
reproducing the issue once [1]. Since this can only be reproduced on
Alexander and Konstantin's laptops, running an older macos [2] and running
MDM, I'm for now considering this issue to not be reproducible outside of that
environment. That's deeply unsatisfying, but I just don't see what else I
could do.

RMT, note that there were two issues in this thread, the original report by
Tom has been addressed (in e9a3615a522). I guess the best thing would be to
split the open items entry into two?

Greetings,

Andres Freund

[1] Rather impressed at how stable our tests are right now, I've barely hit
any independent issues. That definitely wasn't always the case.

[2] I tried various versions of macos, without success

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-07-21 23:22:53 Re: track generic and custom plans in pg_stat_statements
Previous Message Sami Imseih 2025-07-21 23:13:02 Re: track generic and custom plans in pg_stat_statements