[PR #8086/66ea16ce backport][3.117] Speed up RepositoryVersion saves on add/remove content - #8093
Merged
dralley merged 1 commit intoSep 11, 2026
Conversation
Assisted-by: gpt-5.6-sol (cherry picked from commit 66ea16c)
4 tasks
dralley
approved these changes
Sep 11, 2026
dralley
deleted the
patchback/backports/3.117/66ea16ce236bce27f6a2088dedab2d98096c2ef0/pr-8086
branch
September 11, 2026 16:27
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.
This is a backport of PR #8086 as merged into main (66ea16c).
Was asking sol to take a look at our RepoContent/content_ids problem and it pointed this out. Postgres can't optimize the update to be on the HOT path since the indexes become targets without specifying the fields, or so the AI says. Can't hurt
Assisted-by: gpt-5.6-sol
📜 Checklist
See: Pull Request Walkthrough