This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Verify valid state after updating spatial index #208
Merged
Conversation
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
We're seeing some rare exceptions in production that seemed to be caused by the spatial index getting into an invalid state, where it implies the existence of rows beyond the end of the last buffer row. This carries a cost but we want to find out if and when this is happening in production.
maxbrunsfeld
pushed a commit
that referenced
this pull request
Feb 14, 2017
Verify valid state after updating spatial index
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
1.14-releases, we'll need to cherry-pick atom/atom@2ad6f83 to that branch.We're seeing some rare exceptions in production that seemed to be caused by the spatial index getting into an invalid state, where it implies the existence of rows beyond the end of the last buffer row. This carries a cost but we want to find out if and when this is happening in production.
/cc @maxbrunsfeld