Re: Non-reproducible AIO failure

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Konstantin Knizhnik <knizhnik@garret.ru>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-06-17T15:11:13Z
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

On 2025-06-17 18:08:30 +0300, Konstantin Knizhnik wrote:
> 
> On 17/06/2025 4:47 pm, Andres Freund wrote:
> > > I and Alexandr are using completely different devices with different
> > > hardware, OS and clang version.
> > Both of you are running Ventura, right?
> > 
> No, Alexandr is using darwin23.5

I.e. Sonoma.


> Alexandr also noticed that he can reproduce the problem only with
> --with-liburing.
> And  I am not using it.

That must be a misunderstanding - liburing is linux only.



> > I guess
> >    kextstat -l|grep -v com.apple
> > might suffice.
> 
> kextstat -l| grep -v com.apple
> Executing: /usr/bin/kmutil showloaded --list-only
> No variant specified, falling back to release

Thanks.

Greetings,

Andres Freund