From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Subject: | Bring atomic flag fallback up to snuff |
Date: | 2018-04-06 23:38:54 |
Message-ID: | 20180406233854.uni2h3mbnveczl32@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
As Daniel pointed out in:
https://postgr.es/m/FB948276-7B32-4B77-83E6-D00167F8EEB4@yesql.se the
pg_atomic_flag fallback implementation is broken. That has gone
unnoticed because the fallback implementation wasn't testable until now:
- /* ---
- * Can't run the test under the semaphore emulation, it doesn't handle
- * checking two edge cases well:
- * - pg_atomic_unlocked_test_flag() always returns true
- * - locking a already locked flag blocks
- * it seems better to not test the semaphore fallback here, than weaken
- * the checks for the other cases. The semaphore code will be the same
- * everywhere, whereas the efficient implementations wont.
- * ---
- */
and flags weren't used until recently.
The attached fixes the bug and removes the edge-cases by storing a value
separate from the semaphore. I should have done that from the start.
This is an ABI break, but given the fallback didn't work at all, I don't
think that's a problem for backporting.
Fix attached. Comments?
Greetings,
Andres Freund
Attachment | Content-Type | Size |
---|---|---|
0001-Fix-and-improve-pg_atomic_flag-fallback-implementati.patch | text/x-diff | 4.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-04-06 23:39:10 | Re: Parallel index creation does not properly cleanup after error |
Previous Message | Stephen Frost | 2018-04-06 23:31:56 | Re: Online enabling of checksums |