@steinbdj put in a bunch of recording merges using the mass merge script, along with a note that the lengths match well. The auto-comment that the script puts in claims they do too… but they don’t.
https://musicbrainz.org/edit/48088350 for example claims same track time. But it’s actually 2:44 vs. 3:06, a rather significant difference. Checking the recordings, ¾ of the album track times agree with the 2:44, but it also has a 3:06 on it. Seems like the mass-merge script used that time, ignoring the majority of them (I’d guess that’s the release that was targeted)… Also really weird that the same catalog number but released in different countries has different times.
Of course, it looks like a couple are missing disc IDs and one of the ones that has them doesn’t match the track times. So maybe it’s just data entry error, copied from release to release… One is also an impressively ahead of its time digital media release from 1986!
I guess I’m leaning towards the merge is correct, and the track times in the database are probably bogus. But it seems like the mass merge script ought to notice weird discrepancies like this.
[edit: I have this release. I have one with the bar code ending with a 9, catalog 415 132-2—so one of the two claiming 2:44. Both the printed booklet and the disc itself give the time as 3:06. So the times are probably just wrong. Interestingly, my disc ID matches the disc ID on the …8 barcode release. I suspect the two 9 releases should be merged and the only difference between the 8 and 9 ones is UPC vs. EAN.]