I think these numerical constraints are because range trees use numerical averages to construct themselves. This is important for OVERLAPS queries common with dates. But you could construct interval tree indexes lexicographically using text but they are quite uncommon. It’s something I’ve experimented with a decent amount though.

https://github.com/ccorcos/database-experiments/blob/master/...