Add indexes on serialized_dag and dag_code#69391
Open
justinpakzad wants to merge 1 commit into
Open
Conversation
ashb
approved these changes
Jul 5, 2026
| down_revision = "d2f4e1b3c5a7" | ||
| branch_labels = None | ||
| depends_on = None | ||
| airflow_version = "3.4.0" |
Member
There was a problem hiding this comment.
@vatsrahul1001 Think this is worth including in 3.3.1?
@justinpakzad is the answer is yes then it would be easier if you could update this pr to use 3.3.1 as the version
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.
This PR adds indexes on the dag_id columns of the serialized_dag and dag_code tables. This should avoid full table scans when fetching the latest serialized Dag or Dag code by dag_id.
Note - this a continuation of #64311, which was closed due to inactivity. Thanks to the author for the original implementation.
closes: #60883
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.