Repository navigation
Conversation
Contributor
|
@joshua-spacetime already introduced a limit exemption mechanism in 009a889. I'd prefer to settle on either the one proposed here, or make the existing one accessible for this purpose, but not have two distinct ways to disable the limit. |
Contributor
Author
I see, then it's up to @joshua-spacetime to decide |
Collaborator
|
Closing as duplicate of #6658 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Changes
Make sure that databases will startup no matter the memory limit. For a database that is starting up, if it reaches the memory limit on transaction reply run eviction if possible (same as before) and if not disable the hard limit until replay is complete.
API and ABI breaking changes
No
Rollback safety impact
n/a
Expected complexity level and risk
2
Testing
Testing was limited to the unit tests