On the performance problem, my guess is that you wrote in a bunch of columns and had those in where clauses. I hope the documentation made it clear that you'd b

On the performance problem, my guess is that you wrote in a bunch of columns and had those in where clauses. I hope the documentation made it clear that you'd be range scanning over data and that you probably wouldn't get desirable performance. In 0.8 and before, the preferred way to model your data was to create many separate series names. This method is currently giving many users great performance. As with all databases, how you model your schema has a significant impact on performance. That being said, it might be that Influx wasn't right for your use case and Postgres is just a better thing to go with. Also, we're not supporting anything prior to the 0.9 series of releases. 0.8 is deprecated and we'll be pushing everyone to move over to 0.9 as we put out more point releases and fix bugs and ensure that it works for their use case over the coming months.