The current version still has the problem that if you do a massive SELECT then it will fill up memory until the process gets killed. That means any ad-hoc quer

The current version still has the problem that if you do a massive SELECT then it will fill up memory until the process gets killed. That means any ad-hoc query can trivially crash your server. That's pretty serious. It's even worse if the ingest is using statsd-influxdb-backend with udp since during the crash you'll lose data. Do you really think it's ok for a novice user to be able to crash the server from your web gui if they make a minor mistake (e.g something like SELECT value FROM /series.*/ not realizing how many series their regex actually applies to until it's too late and the has gui stopped responding)? I think it's common in databases that if you throw a massive query at it that the server doesn't have the resources to handle, things will go wrong. This thinking is worse then wrong. Not only is it wrong - a simple unqualified select won't crash any "common" database - it makes anyone with any "common" database experience doubt your other claims.