2 ms·
Nearly all usecases for this seem to be recreating a time series database... Postgres isn't a great TSDB - the indexes don't understand columns that will only
by londons_explore 4y ago
Nearly all usecases for this seem to be recreating a time series database...
Postgres isn't a great TSDB - the indexes don't understand columns that will only have updates at one end, it doesn't do column compression, range queries are expensive, etc.
Perhaps it's time to just set up a time series database... Like influxDB.
- jpgvm 4y agoOr just use TimescaleDB which is competitive on most axes but already PG.
- _joel 4y ago+1 for Timescale. Used it for a few RNN projects and it's been great.
- GordonS 4y agoAnd I +1 your +1, we've been using it in prod for 2 years or so.
- LoriP 4y agoThanks for the mentions (and for using TimescaleDB). If anyone's curious about TimescaleDB, it's packaged as an extension to Postgres, optimizing for performance, storage, and analysis of time series data. Implementing columnar compression algorithms is a big part of the secret sauce that makes TimescaleDB a popular choice with Postgres and SQL developers. You can read more about that on the Timescale blog (I'm Timescale's community manager btw). https://www.timescale.com/blog/search/?query=compression https://www.timescale.com/blog/search/?query=compression If anyone's curious, the youtube channel may be a good place to start, especially this playlist https://www.youtube.com/playlist?list=PLsceB9ac9MHTtM1XWONMRnCBcncb8jpIu https://www.youtube.com/playlist?list=PLsceB9ac9MHTtM1XWONMR...
- mritchie712 4y agoor clickhouse!
- dengolius 4y ago+1 have a good experience with using it
- dengolius 4y agoI recommend to use VictoriaMetrics instead of using InfluxDB for many reasons. PostgreSQL is good SQL database for different purposes but as TSDB on a big installations it works not really well.