-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Fixes #27158: ingestion slowdown from tag_usage seq-scan on Postgres #27745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sonika-shah
wants to merge
1
commit into
main
Choose a base branch
from
fix-27158-tag-usage-postgres-index
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
1 change: 1 addition & 0 deletions
1
bootstrap/sql/migrations/native/1.12.8/mysql/postDataMigrationSQLScript.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| -- Placeholder for 1.12.8 MySQL post-data migration script |
4 changes: 4 additions & 0 deletions
4
bootstrap/sql/migrations/native/1.12.8/mysql/schemaChanges.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| -- Placeholder for 1.12.8 MySQL schema changes | ||
| -- The Postgres-side fix for #27158 has no MySQL counterpart: MySQL's | ||
| -- 1.11.0 indexes were already non-partial (no partial-index syntax in | ||
| -- MySQL), so the regression that hit Postgres did not affect MySQL. |
1 change: 1 addition & 0 deletions
1
bootstrap/sql/migrations/native/1.12.8/postgres/postDataMigrationSQLScript.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| -- Placeholder for 1.12.8 PostgreSQL post-data migration script |
27 changes: 27 additions & 0 deletions
27
bootstrap/sql/migrations/native/1.12.8/postgres/schemaChanges.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| -- Issue #27158: tag_usage seq-scan on Postgres. #24063 dropped the | ||
| -- `state = 1` predicate that 1.11.0's partial indexes required. | ||
| -- Fix: add a single-col index, and drop the `WHERE state = 1` filter | ||
| -- from the existing partials so query changes can't invalidate them. | ||
|
|
||
| CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_tag_usage_targetfqnhash_lower_pattern | ||
| ON tag_usage (targetfqnhash_lower text_pattern_ops); | ||
|
|
||
| DROP INDEX CONCURRENTLY IF EXISTS idx_tag_usage_target_prefix_covering; | ||
| CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_tag_usage_target_prefix_covering | ||
| ON tag_usage (source, targetfqnhash_lower text_pattern_ops) | ||
| INCLUDE (tagFQN, labelType, state); | ||
|
|
||
| DROP INDEX CONCURRENTLY IF EXISTS idx_tag_usage_tagfqn_prefix_covering; | ||
| CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_tag_usage_tagfqn_prefix_covering | ||
| ON tag_usage (source, tagfqn_lower text_pattern_ops) | ||
| INCLUDE (targetFQNHash, labelType, state); | ||
|
|
||
| DROP INDEX CONCURRENTLY IF EXISTS idx_tag_usage_join_source; | ||
| CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_tag_usage_join_source | ||
| ON tag_usage (tagFQNHash, source) | ||
| INCLUDE (targetFQNHash, tagFQN, labelType, state); | ||
|
|
||
| CREATE EXTENSION IF NOT EXISTS pg_trgm; | ||
| DROP INDEX CONCURRENTLY IF EXISTS gin_tag_usage_targetfqn_trgm; | ||
| CREATE INDEX CONCURRENTLY IF NOT EXISTS gin_tag_usage_targetfqn_trgm | ||
| ON tag_usage USING GIN (targetFQNHash gin_trgm_ops); | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description references applying the fix under
native/2.0.1/postgres/schemaChanges.sql, but the actual change is introduced innative/1.12.8/postgres/schemaChanges.sql. Please align the PR description (and/or title) with the versioned migration directory that is actually being modified to avoid confusion during verification/rollout.