The more I think about it, this falls into a broader 'resource management' or a 'qos' solution, even if it is a very naive implementation. The point being to constrain certain users to limit their impact on the database, while giving others more resources or priority. This matters a lot less now that we have only a small number of consumers, but will be a bigger topic when more consumer types start to want some query time on the DB.