Pekka Enberg 6c48cb7043 Merge 'core: Use sequential consistency for atomics by default' from Pekka Enberg ...

We use relaxed ordering in a lot of places where we really need to
ensure all CPUs see the write. Switch to sequential consistency, unless
acquire/release is explicitly used. If there are places that can be
optimized, we can switch to relaxed case-by-case, but have a comment
explaning *why* it is safe.

Closes #3193

2025-09-18 14:19:54 +03:00

..

btree.rs

core/storage: Use AtomicU32 for Pager::page_size

2025-09-18 11:33:32 +03:00

buffer_pool.rs

core: Use sequential consistency for atomics by default

2025-09-18 13:38:13 +03:00

checksum.rs

Add checksums behind a feature flag

2025-09-13 11:00:39 +05:30

database.rs

rename method to verify_checksum

2025-09-13 11:00:39 +05:30

encryption.rs

clean up encryption feature flag usage

2025-09-17 16:30:51 +05:30

mod.rs

Add checksum module

2025-09-13 11:00:37 +05:30

page_cache.rs

core: Use sequential consistency for atomics by default

2025-09-18 13:38:13 +03:00

pager.rs

Merge 'core: Use sequential consistency for atomics by default' from Pekka Enberg

2025-09-18 14:19:54 +03:00

slot_bitmap.rs

Rename page -> slot for arenas + buffer pool

2025-08-12 11:36:49 -04:00

sqlite3_ondisk.rs

Merge 'core: Use sequential consistency for atomics by default' from Pekka Enberg

2025-09-18 14:19:54 +03:00

state_machines.rs

refactor/idx_insert: move seeking to VDBE instead of BTreeCursor

2025-08-19 19:04:42 +03:00

wal.rs

core: Use sequential consistency for atomics by default

2025-09-18 13:38:13 +03:00