Remove UNIQUE constraints that cause btree overflow#3
Merged
jakebromberg merged 1 commit intomainfrom Feb 14, 2026
Merged
Conversation
…st names The btree index backing UNIQUE (release_id, artist_name) overflows PostgreSQL's 2,704-byte limit when artist_name exceeds ~900 bytes. These constraints are redundant: import_csv.py deduplicates via unique_key before COPY, and dedup_releases.py drops them anyway during copy-swap.
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
1 participant
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.
Summary
UNIQUE (release_id, artist_name)fromrelease_artistandUNIQUE (release_id, track_sequence, artist_name)fromrelease_track_artistincreate_database.sqlartist_nameexceeds ~900 bytes (PostgreSQL's 2,704-byte page limit)import_csv.pydeduplicates rows viaunique_keybefore COPY, anddedup_releases.pydrops them during copy-swap anywayTest plan
pytest -m postgres) -- addedtest_no_unique_constraints_on_child_tablesto verify constraints are absent