Re: Non-reproducible AIO failure

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Konstantin Knizhnik <knizhnik@garret.ru>
Cc: Alexander Lakhin <exclusion@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-06-19T14:36:20Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. aio: Stop using enum bitfields due to bad code generation

  2. amcheck: Fix posting tree checks in gin_index_check()

  3. aio: Add missing memory barrier when waiting for IO handle

Hi,

On 2025-06-19 17:02:18 +0300, Konstantin Knizhnik wrote:
> On 18/06/2025 7:08 pm, Andres Freund wrote:
> > Hi,
> >
> > On 2025-06-18 10:32:08 +0300, Konstantin Knizhnik wrote:
> > > On 17/06/2025 6:08 pm, Andres Freund wrote:
> > > > I don't think it can - this must be an independent bug from the one that Tom
> > > > and I were encountering.
> > > I see... It's a pity.
> > Indeed.
> >
> > Konstantin, Alexander, can you share what commit you're testing and what
> > precise changes have been applied to the source?
>
> I am using most recent master: 0cf205e122ae0fe9333ccf843c2269f13ddc32fc
>
> By the way - still not been able to reproduce assertion failure at most
> recent MacPro (Apple M4 Pro) with Sequoia 15.5.

So for some reason this apparently can only be reproduced on older macos - we
know it's not the older compiler, because I couldn't reproduce it on the same
compile version as alexander, on an m1 that was running sequoia. That's really
really weird. I guess I'll try to see if i can reproduce it on an older macos
in a VM, running on an m4.

Greetings,

Andres