TimescaleDB vs. InfluxDB: built differently for time-series data
Does anyone have thoughts on why Postgres shouldn't provide:- Automatic sharding of tables per-"shard key".- Automatic sharding of those keyed shards by the range of some primary index.Doesn't this get you 90%+ of the way there? (There's no "adaptive" time bucketing, I guess.)For the record, I am a veteran of a naive Postgres time series scheme that was brought to its knees by seek times.