Handling unique indexes on large data in PostgreSQL

Something went wrong! Hang in there while we get back on track A month ago, during a release to production, the feature I was working on failed to deploy due to a PostgreSQL restriction. It turned out to be a surprisingly fun and comprehensive learning moment. Backstory I have been working on a pretty huge release where we needed to: Add new functionality to our core feature. Remove all duplicated

[yosuke_furukawa]

おもろい。Postgresで大量データに対してユニークインデックスをはろうとするとB-Treeインデックスの制約により、エラーになる。MD5とかsha-1に変換してから貼ろうっていうテク。