If you are running a mirror, you may have seen replication packet #162718 fail to apply with the following error:
Failed query:
'INSERT INTO musicbrainz.tag (id, name, ref_count) VALUES (?, ?, ?)'
(259975 girl group 0)
23505 DBD::Pg::st execute failed: ERROR: duplicate key value violates unique constraint "tag_idx_name"
DETAIL: Key (name)=(girl group) already exists. [for Statement "INSERT INTO musicbrainz.tag (id, name, ref_count) VALUES (?, ?, ?)" with ParamValues: 1='259975', 2='girl group', 3='0']This occurs because the index tag_idx_name was temporarily corrupted in production after yesterday’s database switchover, due to an ICU collation version mismatch. This allowed people to enter tags with duplicate names.
Since then we’ve fixed the broken packets, and published the fixed versions.
A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.
The git tag is v-2023-10-24-hotfix.
Notes
- If you encountered the error above, you’ll have a “previously aborted load,” and must update your MusicBrainz Server to
v-2023-10-24-hotfix. After that, replication should operate smoothly without any further action being needed. - If you haven’t replicated up to packet #162718 yet, then no action is needed.
We apologize for the inconvenience. We’re improving our database upgrade process to always rebuild indexes using ICU collations.
Fixed Bug
- [MBS-13333] – Replication is blocked by tag duplicates
MetaBrainz Blog 