Re:Migrating Graphite from SQLite to PostgreSQL
by Someone on Sunday December 15, 2013 @05:42AM
(#6908979)
The way I read this, this _is_ a problem with SQLite (somewhat). Both schemas limit the length of graph names, but SQLite ignores that part of the schema.
One can discuss whether it is a good idea to have that arbitrary, low limit, but that is not what this is about.
I agree that there are plenty of reasons to use SQLite in production. IMO, the conclusion should have been that one should run the same database in development, test, and production.
Re:Migrating Graphite from SQLite to PostgreSQL
by obfuscurity_ on Sunday December 15, 2013 @01:56PM
(#6910346)
Excuse my french, but you're an idiot. I don't know if you simply didn't read the article, or are incapable of grasping the facts within.
TL;DR - graphite devs don't understand postgresql, graphite user misdiagnoses the problem and blames sqlite for it.