-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checking for already opened LMDB Environments #180
Labels
enhancement
New feature or request
Milestone
Comments
Kerollmops
changed the title
Checking for LMDB Environnements already opened
Checking for already opened LMDB Environments
Jul 10, 2023
@Kerollmops would suggest removing from 0.20.0 this issue the solution may cause more trouble than the initial issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Heed strive to pursue opening LMDB safely, so a database environment must be opened only once inside a process address space.
Any subsequent opening shall return the corresponding already opened environment.
It was done with
Path
Canonization but it fails to tackle symlinks, hardlinks and renaming/move of the whole database environment (both locks and database).In an ideal world the environment already open checking must prevail:
same_file::Handle
#179 (comment)[ ] Access through hardlinkNot possible since hard_link only apply to files and we track dir for envs.Related pull requests/ Issue
Flags::MdbNoSubDir
flag requires target file to exists #145 (comment)same_file::Handle
#179Open question
Is Canonization still pertinant if we check already-openned by Unix: (device/inode) Windows: (Driver/fileID) through same_file?
How to do it compatible with windows without lefting file open.
Problems
Lmdb rely on Unixes on posix filelocking through fnctl
The text was updated successfully, but these errors were encountered: