Re: Non-reproducible AIO failure

Konstantin Knizhnik <knizhnik@garret.ru>

From: Konstantin Knizhnik <knizhnik@garret.ru>

To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-06-17T13:43:05Z

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 →

aio: Stop using enum bitfields due to bad code generation
- ce161b194e84 18.0 landed
- 5865150b6d53 19 (unreleased) landed
amcheck: Fix posting tree checks in gin_index_check()
- 0cf205e122ae 18.0 cited
aio: Add missing memory barrier when waiting for IO handle
- e9a3615a5224 18.0 landed

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.

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

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