-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
Apparently a too large (but sadly "legitimate") track/recording title causes issues with Postgres indexes. This is the release: https://musicbrainz.org/release/f5a676e6-8fcd-43de-ab0f-5d864d045e8e
The issue, as reported on IRC:
54000 DBD::Pg::st execute failed: ERROR: index row requires 27120 bytes, maximum size is 8191 [for Statement "UPDATE musicbrainz.track SET last_updated = ?, name = ? WHERE id = ?" with ParamValues: 1='2024-04-08 06:00:13.948197+00', 2='Although I hate it when titles look like this, And Much Prefer Them Like This, I wont capitalize every word as its incredibly annoying to do with titles this long. Anyways though, this is another }}{{13:10 overly long lo-bit (low-bit) 8kbps wall thats very long with a long title that nobody will bother to listen to nor read, yet I feel some bizarre drive to make, when in reality, I would rather be watching anime or playing a game (the game) instead (also, lol, how many tracks have I made with that theme?). Honestly though, isn't it annoying when like, you want to relax and do something, but your mind is just too dead or stressed to }}{{{}13:10 do it? It happens far too often and drives me insane. Also, I forgot that I wanted this title to just be nonsense and not one of these "noise diaries". Does it really matter though? I feel only a few will read titles like this, probably just Antimatter Prism, since they like absurdly long titles as well. Maybe I should revive an old split idea I had with a friend...', 3='42013256']13:10 at /musicbrainz-server/admin/replication/../../lib/Sql.pm line 123.