max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-23 14:36:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

More detail on why read-only mode disables locking.

Browse source
This commit is contained in:
Ben Radford 2023-06-15 13:22:17 +01:00
parent c47f744e05
commit 264b644c53
No known key found for this signature in database
GPG key ID: 9DF5D4640AB888D5
1 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
src/libutil/experimental-features.cc
View file

@ -223,11 +223,14 @@ constexpr std::array<ExperimentalFeatureDetails, 14> xpFeatureDetails = {{
Set this parameter to `true` to allow stores with databases on read-only Set this parameter to `true` to allow stores with databases on read-only
filesystems to be opened for querying; ordinarily Nix will refuse to do this. filesystems to be opened for querying; ordinarily Nix will refuse to do this.
Enabling this setting disables the locking required for safe concurrent This is because SQLite requires write access to the database file to perform
access, so you should be certain that the database will not be changed. the file locking operations necessary for safe concurrent access. When `read-only`
While the filesystem the database resides on might be read-only to this is set to `true`, the database will be opened in immutable mode.
process, consider whether another user, process, or system, might have
write access to it. Under this mode, SQLite will not do any locking at all, so you should be certain
that the database will not be changed. While the filesystem the database resides
on might be read-only to this process, consider whether another user, process,
or system, might have write access to it.
)", )",
}, },
}}; }};