4121 Fix RENAME TO/SET SCHEMA on distributed hypertable
4122 Fix segfault on INSERT into distributed hypertable
4142 Ignore invalid relid when deleting hypertable
4159 Fix ADD COLUMN IF NOT EXISTS error on compressed hypertable
4161 Fix memory handling during scans
4176 Fix remote EXPLAIN with parameterized queries
4181 Fix spelling errors and omissions
4186 Fix owner change for distributed hypertable
4192 Abort sessions after extension reload
4193 Fix relcache callback handling causing crashes
4199 Remove signal-unsafe calls from signal handlers
4219 Do not modify aggregation state in finalize
- Continuous aggregates with compression
- time_bucket_ng support for N months and timezones on cont. aggregates
- Query planning performance is improved for hypertables with a large
number of chunks.
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
The following distfiles could not be fetched (some may be only fetched
conditionally):
./databases/cstore/distinfo D6.data.ros.gz
./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz
The release fixes continuous aggregate refresh for postgres 12.8 and
13.4, a crash with ALTER TABLE commands and a crash with continuous
aggregates with HAVING clause.
This release adds new experimental features since the 2.3.1 release:
- APIs for chunk manipulation across data nodes
- The time_bucket_ng function, a newer version of time_bucket
PostgreSQL 11 is deprecated and not supported with TimescaleDB 2.4.
This maintenance release contains bugfixes since the 2.3.0 release. We
deem it moderate priority for upgrading. The release introduces the
possibility of generating downgrade scripts, improves the trigger
handling for distributed hypertables, adds some more randomness to
chunk assignment to avoid thundering herd issues in chunk assignment,
and fixes some issues in update handling as well as some other bugs.
This release adds support for inserting data into compressed chunks
and improves performance when inserting data into distributed hypertables.
Distributed hypertables now also support triggers and compression policies.
The bug fixes in this release address issues related to the handling
of privileges on compressed hypertables, locking, and triggers with
transition tables.
Major Features
Add distributed restore point functionality
SkipScan to speed up SELECT DISTINCT
Bugfixes
Refactor and harden size and stats functions
Reduce memory usage for distributed inserts
Fix extremely slow multi-node order by queries
Fix chunk index column name mapping
Keep Append pathkeys in ChunkAppend
timescale-license is very hard to understand, but there is clearly no
grant of permission to distribute derived works. Permission is
perhaps granted to distribute unmodified versions, but it's
conditioned on compliance with hard to understand terms and limited
based on purpose of use.
TimescaleDB 2.0 adds the much-anticipated support for distributed
hypertables (multi-node TimescaleDB), as well as new features and
enhancements to core functionality to give users better clarity and
more control and flexibility over their data.
This release also adds:
- Support for user-defined actions, allowing users to define,
customize, and schedule automated tasks, which can be run by the
built-in jobs scheduling framework now exposed to users.
- Significant changes to continuous aggregates, which now separate the
view creation from the policy. Users can now refresh individual
regions of the continuous aggregate materialized view, or schedule
automated refreshing via policy.
- Redesigned informational views, including new (and more general)
views for information about hypertable's dimensions and chunks,
policies and user-defined actions, as well as support for multi-node
TimescaleDB.
- Moving all formerly enterprise features into our Community Edition,
and updating Timescale License, which now provides additional (more
permissive) rights to users and developers.
Some of the changes above (e.g., continuous aggregates, updated
informational views) do introduce breaking changes to APIs and are not
backwards compatible. While the update scripts in TimescaleDB 2.0 will
upgrade databases running TimescaleDB 1.x automatically, some of these
API and feature changes may require changes to clients and/or upstream
scripts that rely on the previous APIs. Before upgrading, we recommend
reviewing upgrade documentation at docs.timescale.com for more details.
TimescaleDB is an open-source database designed to make SQL scalable for
time-series data. It is engineered up from PostgreSQL and packaged as a
PostgreSQL extension, providing automatic partitioning across time and space
(partitioning key), as well as full SQL support.
WWW: https://github.com/timescale/timescaledb
