Make DB_CLOSE_ON_EXIT safer #3846
Merged
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.
DB_CLOSE_ON_EXITis one of the most popular misused dangerous settings.FALSEfor in-memory databases to avoid registration of shutdown hook. I'm not sure about that, but I think we don't really need to explicitly close any in-memory databases on VM shutdown. Anyway, it is possible to restore this feature withDB_CLOSE_ON_EXIT=TRUE.TRUEas it should, but if it was set toFALSEexplicitly, the shutdown hook is registered anyway and VM shutdown event executes aCHECKPOINTcommand to flush data on disk for more safety.@grandinj