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-17T13:47:37Z
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-17 16:43:05 +0300, Konstantin Knizhnik wrote:
> On 17/06/2025 4:35 pm, Andres Freund wrote:
> > Konstantin, Alexander - are you using the same device to reproduce this or
> > different ones? I wonder if this somehow depends on some MDM / corporate
> > enforcement tooling running or such.
> > 
> > What does:
> > - profiles status -type enrollment
> > - kextstat -l
> > show?
> 
> 
> I and Alexandr are using completely different devices with different
> hardware, OS and clang version.

Both of you are running Ventura, right?


> profiles status -type enrollment
> Enrolled via DEP: No
> MDM enrollment: Yes (User Approved)
> MDM server: https://apple.mdm.jumpcloud.com/command

So it is enrolled in MDM, which, I guess, means there's some kernel component
running...


> `kextstat -l` output very long list, should I post it all or search for some
> particular pattern?

I guess
  kextstat -l|grep -v com.apple
might suffice.

Greetings,

Andres Freund