tsdb/index: export sentinel error for symbol table size exceeded#18057
Merged
bboreham merged 1 commit intoprometheus:mainfrom Feb 10, 2026
Merged
tsdb/index: export sentinel error for symbol table size exceeded#18057bboreham merged 1 commit intoprometheus:mainfrom
bboreham merged 1 commit intoprometheus:mainfrom
Conversation
Signed-off-by: Patryk Prus <p@trykpr.us>
bboreham
approved these changes
Feb 10, 2026
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
2 participants
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.
Similar to #17773, we want to detect and handle "symbol table size exceeds 4294967295 bytes" errors without having to rely on string matching. This PR adds a sentinel error that can be detected using
errors.Is.Change isn't user-facing, so no CHANGELOG required.
Which issue(s) does the PR fix:
Does this PR introduce a user-facing change?