This repository has been archived by the owner on Mar 9, 2019. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #706.
This PR causes the db to revert to
mmap(db, db.datasz)
if the call tommap(db, minsz)
fails. The original error is still returned, so callers will see"mmap failure"
returned fromdb.Update
. I also wrapped this error in a new type, so that callers can check for it explicitly. This is good to have, since I imagine applications will want to panic instead of continuing to attempt moredb.Update
calls. Another option would be to add aPanicOnFailedMmap
flag so that bolt will automatically panic under these conditions.I'm not 100% sure that this code is safe, but I've confirmed that it resolves the segfault bug, and it appears that calls to
db.View
will succeed even after mmap failure.