3 ms·
You start to miss constraints when you use a database system which has none. I used Postgres to store various sensor data (some Raspberry, ESP and other "mini"
by gsich 9y ago
You start to miss constraints when you use a database system which has none.
I used Postgres to store various sensor data (some Raspberry, ESP and other "mini" stuff). Then tried InfluxDB, mainly because Grafana supported it, while Postgres did not (it does now!).
Now there are sensor malfunctions, due to old age, no proper connection, bugs or whatever. A Temperature sensor which shows 85 °C while only being capable of 50 °C? You could capture that in the application, but this is cumbersome. Just do it in the database, constraint "temperature < 50" and you are done.
To top it off, deleting wrong data in InfluxDB is a real pain.
- jadbox 9y agoDid you move back to Postgres? What are some things you did to bring some of the things you needed from Influx into PG (like rolling aggregations)?
- gsich 9y agoNo. At least not yet. Rolling aggregations are broken in InfluxDB aswell.
- nopzor 9y agoThanks for the grafana shoutout. Glad you find the Postgres support in it useful. Out of curiosity, re: constraints in your example couldn't you easily do something like removeAboveValue(50) when retrieving your data from these faulty sensors? It seems like basic constraints, windowing, etc should be part and parcel of most time series databases?