Skip to content
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

Document the safety issues with the unnamed database #40

Open
Kerollmops opened this issue Mar 18, 2020 · 0 comments · Fixed by #128
Open

Document the safety issues with the unnamed database #40

Kerollmops opened this issue Mar 18, 2020 · 0 comments · Fixed by #128
Labels
bug Something isn't working documentation Improvements or additions to documentation good first issue Good for newcomers
Milestone

Comments

@Kerollmops
Copy link
Member

Kerollmops commented Mar 18, 2020

LMDB has an important restriction on the unnamed database when named ones are opened the names of the named databases are stored as keys in the unnamed one and are immutable.

I faced a big bug that triggered a SIGSEGV when copying all of the entries of one unnamed database into another env, heed tried to write the values associated with the opened named databases multiple times, it triggered SIGSEGV sometimes.

I didn't take the time to reproduce this behavior, but we must, at least, document it!

@Kerollmops Kerollmops added bug Something isn't working documentation Improvements or additions to documentation good first issue Good for newcomers labels Mar 18, 2020
@Kerollmops Kerollmops added this to the v0.20.0 milestone Jan 11, 2023
@Kerollmops Kerollmops reopened this Jan 11, 2023
@Kerollmops Kerollmops modified the milestones: v0.20.0, v0.21.0 Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant