Re: Non-reproducible AIO failure - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: Non-reproducible AIO failure
Date
Msg-id f1242051-7cd0-413c-b9ea-7ebcf7f6bc96@garret.ru
Whole thread Raw
In response to Re: Non-reproducible AIO failure  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Non-reproducible AIO failure
List pgsql-hackers
On 24/08/2025 3:38 PM, Thomas Munro wrote:
> That's also how open source clang 17 compiles it if you rip out the
> bitfield.  I guess if you do that, you won't be able to reproduce
> this, Alexander?  Something like:

I think that we have made this experiment at the very beginning and as 
far as I remembered we were not able to reproduce the problem with 
replaced bitfields. In theory even replacing bitfield with in should not 
avoid race condition, because they are still shared the same cache line.
But practice doesn't confirm it:)


I tried to create small test reproducing this data flow.
But still failed to find and problem with this test.
May be somebody can change this test to be more similar with real AIO 
dataflows?

Attachment

pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: Re: Inconsistent update in the MERGE command
Next
From: Tom Lane
Date:
Subject: Re: Identifying function-lookup failures due to argument name mismatches