index car_blocks.file_id to fix FK cascade scans#665
Merged
Conversation
without this index, ON DELETE SET NULL from files.id to car_blocks.file_id causes a full-table sequential scan of car_blocks for every file being deleted. on a billion-row car_blocks table this makes file deletion effectively impossible -- the healthcheck reaper in prod wedged for 5 months because of exactly this. add gorm:"index" to CarBlock.FileID (CarID already has one). add a regression test that asserts both FK columns plus cid are indexed, so this doesn't silently regress again.
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.
CarBlock.FileIDwas unindexed, soON DELETE SET NULLfromfiles.idtriggered a full seq scan ofcar_blocksper deleted file. At ~1.5B rows this wedged the reaper's files phase for months.gorm:"index"onCarBlock.FileID(matchingCarID)CarID,FileID,CIDare all indexed