Publishing details

Changelog

timescaledb-postgresql-10 (1.6.0~ubuntu19.04) disco; urgency=low

  * This release adds major new features and bugfixes since the 1.5.1 release. We deem it moderate priority for upgrading.

  * The major new feature in this release allows users to keep the aggregated data in a continuous aggregate while dropping the raw data with drop_chunks. This allows users to save storage by keeping only the aggregates.

  * The semantics of the refresh_lag parameter for continuous aggregates has been changed to be relative to the current timestamp instead of the maximum value in the table. This change requires that an integer_now func be set on hypertables with integer-based time columns to use continuous aggregates on this table.

  * We added a timescaledb.ignore_invalidation_older_than parameter for continuous aggregatess. This parameter accept a time-interval (e.g. 1 month). if set, it limits the amount of time for which to process invalidation. Thus, if timescaledb.ignore_invalidation_older_than = '1 month', then any modifications for data older than 1 month from the current timestamp at modification time may not cause continuous aggregate to be updated. This limits the amount of work that a backfill can trigger. By default, all invalidations are processed.

 -- Timescale <email address hidden>  Wed, 15 Jan 2020 20:14:50 +0000

Available diffs

Builds

Built packages

Package files