Repository navigation
Drop forensic raw-message trigram index - #541
Merged
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
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.
MessageReceived inserts have shown multi-second stalls, with synchronous maintenance of the forensic raw-message GIN index a suspected contributor. Add an idempotent V55 migration using DROP INDEX CONCURRENTLY to remove that index without blocking table writes. Forensic text searches remain available but may be slower; existing migration history is preserved.
Validation: staged diff check and mandatory pre-commit comment gate passed. Local migration execution was unavailable because PostgreSQL/container tooling is not installed; the Vahter CI suite validates the migration chain.