I'm having this query which is consuming crazy amounts of CPU on my staging environment (using Postgres, the green bars are CPU and the left part of the graph is "normal" load):

SELECT MIN(id), MAX(id) FROM relation_tuple_transaction WHERE timestamp >= $1

I only have read traffic, no write. When it starts going into this pattern, all checks take multiple minutes (and might be timeout-ing). That looks like a bug in spicedb?