[justinpakzad]

---

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?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {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.

[justinpakzad]

Updated the version to 3.3.1. Given there were already a few 3.4.0 migrations, I had to modify/rename some of the other files in order put it between 3.3.0 and 3.4.0. Also added a test as requested.

[justinpakzad]

Would appreciate another review on this. Thanks.

[justinpakzad]

@ephraimbuddy any thoughts on this?

[ephraimbuddy]

This looks good but I think we should have composite indexes which will be more beneficial in the long run
(dag_id, last_updated) on dagcode and (dag_id, created_at) on serialized_dag

We have queries that actually exercise those paths

[justinpakzad]

This looks good but I think we should have composite indexes which will be more beneficial in the long run (dag_id, last_updated) on dagcode and (dag_id, created_at) on serialized_dag

We have queries that actually exercise those paths

Good call, I've updated them to composite indexes.

[vatsrahul1001]

This change is more suitable for minor release not patch moving to 3.4.0

[justinpakzad]

This change is more suitable for minor release not patch moving to 3.4.0

Makes sense. I've updated it to target 3.4.0.

[github-actions]

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker e24f529 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.