James Guthrie
James Guthrie
The following are my rough notes on things that we can do to improve the user experience of reaching 200k metric samples/s: - max_wal_size - We can provide an actual...
## Description The clockcache is used in 9 caches, but understanding what each of those caches actually does is quite difficult, because few of them expose a clean interface. This...
We currently don't surface to users which versions of these components work together.
This is blocked by https://github.com/timescale/promscale_extension/issues/335
We currently don't test against nightly TimescaleDB, so a new release can break Promscale. For this reason (and others) we should suggest that users use a pinned version of the...
## Description In the database, these ids are stored as INTEGER values which correspond to int32. ## Merge requirements Please take into account the following non-code changes that you may...
The documentation for downsampling with caggs is broken: https://docs.timescale.com/promscale/latest/downsample-data/caggs/#continuous-aggregates-in-promscale. - It doesn't correctly handle the fact that the metric name is mixed-case - The cagg definition fails to load with...
If the telemetry settings are updated in the database (e.g. turning telemetry off), we continue trying to calculate and populate the telemetry data. Link to report from community slack: https://timescaledb.slack.com/archives/C011FC0PPC5/p1654254320294149?thread_ts=1654179336.687629&cid=C011FC0PPC5
In https://github.com/timescale/promscale/pull/1248 we've disabled the multinode e2e tests because they're failing against the latest (development) promscale extension version. That issue is being tracked in https://github.com/timescale/promscale_extension/issues/138. Once we have those issues...
In order to use an extension in Postgres it 1. needs to be installed on disk, and 2. needs to be added to a DB with `CREATE EXTENSION ...;`. Users...