Re: Non-reproducible AIO failure

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Non-reproducible AIO failure
Date: 2025-05-24 11:42:35
Message-ID: CA+hUKGLqUFyOJaPSRSmSZX_PCzCxaRezkfv-nkLRmexb-uTtpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 24, 2025 at 3:17 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> So it seems that "very low-probability issue in our Mac AIO code" is
> the most probable description.

There isn't any macOS-specific AIO code so my first guess would be
that it might be due to aarch64 weak memory reordering (though Andres
speculated that itt should all be one backend, huh), if it's not just
a timing luck thing. Alexander, were the other OSes you tried all on
x86?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message * Neustradamus * 2025-05-24 11:45:29 Please update your contact list: It must be pgsql-hackers@lists.postgresql.org
Previous Message Amit Kapila 2025-05-24 11:16:15 Re: Conflict detection for update_deleted in logical replication