Event Timeline
Comment Actions
Ideally yes. The rev_timestamp should always be 14 bytes like "20190425152513", so making it varbinary is probably costing extra storage (to store the length) rather than saving it.
But I don't think this one can be done as an online change, so actually fixing it might have to wait for the other revision table changes in T161671.