| From: | Konstantin Knizhnik <knizhnik(at)garret(dot)ru> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Nico Williams <nico(at)cryptonector(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, rmt(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Non-reproducible AIO failure |
| Date: | 2025-08-24 18:11:36 |
| Message-ID: | f1242051-7cd0-413c-b9ea-7ebcf7f6bc96@garret.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| race.c | text/plain | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-24 18:47:12 | Re: Identifying function-lookup failures due to argument name mismatches |
| Previous Message | Yugo Nagata | 2025-08-24 17:34:04 | Re: Inconsistent update in the MERGE command |