Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.16.0 #7135

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .unreleased/fix_7055

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/fix_7064

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/fix_7074

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6880

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6895

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6897

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6918

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6920

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_6989

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7018

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7020

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7046

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7048

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7069

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7075

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7101

This file was deleted.

1 change: 0 additions & 1 deletion .unreleased/pr_7108

This file was deleted.

31 changes: 31 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,37 @@
`psql` with the `-X` flag to prevent any `.psqlrc` commands from
accidentally triggering the load of a previous DB version.**


## 2.16.0 (2024-07-18)

This release contains performance improvements and bug fixes since
the 2.15.3 release. We recommend that you upgrade at the next
available opportunity.

Copy link

@iroussos iroussos Jul 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With this release we introduce a lot of performance focused optimizations for DML over compressed chunks.
We also speed up those tricky queries that end up accessing more chunks than needed, by extending chunk
exclusion on compressed hypertables to take into account filters on additional, non partitioning columns.
We also introduce new options for Timescale users that like their Foreign Keys, allowing for FKs from regular tables towards hypertables, but also removing some really annoying locks in the reverse direction that blocked access to referenced tables while compression was running.
Finally, big updates on the Continuous Aggregates front - more types of joins supported, additional equality operators on join clauses and support for joining with multiple regular tables.
**Highlighted features in this release**
* Improved query performance through chunk exclusion on compressed hypertables by using additional columns:
You can now define sparse indexes on compressed chunks for any column with
an integer data type (smallint, int, bigint, serial, bigserial, date, timestamp, timestamptz).
After enabling this feature for a column using the `enable_column_stats` command, Timescale will track min/max
values for that column and use that information to exclude chunks for queries that filter by that column and would
not find any data on those chunks.
* Improved upsert performance by using index scans to verify constraints during inserts on compressed chunks.
This improvement can speed up some ON CONFLICT clauses by more than 100x.
* Improved performance of updates and deletes on all types of compressed chunks, as well as inserts into compressed
chunks with unique constraints by filtering data while accessing the compressed data and before decompressing.
This improvement can speedup significantly a lot of types of DML commands by signaling constraint violations without decompressing or decompressing only when matching records are found in the case of updates, deletes and upserts.
* New ability to add Foreign Keys from regular (non hyper) tables to hypertables, with all types of cascading options supported.
Really useful for hypertables that partition using sequential IDs, but also for some time series use cases.
* Advanced handling of Foreign Keys on compressed chunks do eliminate locking of referenced tables when new
chunks are compressed. No more DML getting blocked on referenced tables while compression runs on a hypertable.
* Improved support for queries on Continuous Aggregates - more types of joins supported (INNER/LEFT and LATERAL joins),
more than one equality operator on join clauses allowed and support for joining with multiple regular tables.
**PostgreSQL 13 support removal announcement**
Following the deprecation announcement for PostgreSQL 13 in TimescaleDB 2.13,
PostgreSQL 13 is not supported starting with TimescaleDB 2.16.
Currently supported PostgreSQL major versions are 14, 15 and 16.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svenklemm @antekresic @fabriziomello can you check and let me know if this looks good & whether I missed anything?

@pallavisontakke I am missing more than a few things that are in the milestone from the description and the list that follows. Like for example the PR by Fabrizio on the CAggs improvements and various other PRs above 7100

@sven check what I wrote about FKs - I am assuming that this will make it for the release. Otherwise, we should remove


**Features**
* #6880: Add support for the array operators used for compressed DML batch filtering.
* #6895: Improve the compressed DML expression pushdown.
* #6897: Add support for replica identity on compressed hypertables.
* #6918: Remove support for PG13.
* #6920: Rework compression activity wal markers.
* #6989: Add support for foreign keys when converting plain tables to hypertables.
* #7020: Add support for the chunk column statistics tracking.
* #7048: Add an index scan for INSERT DML decompression.
* #7075: Reduce decompression on the compressed INSERT.
* #7101: Reduce decompressions for the compressed UPDATE/DELETE.
* #7108 Reduce decompressions for INSERTs with UNIQUE constraints

**Bugfixes**
* #7018: Fix `search_path` quoting in the compression defaults function.
* #7046: Prevent locking for compressed tuples.
* #7055: Fix the `scankey` for `segment by` columns, where the type `constant` is different to `variable`.
* #7064: Fix the bug in the default `order by` calculation in compression.
* #7069: Fix the index column name usage.
* #7074: Fix the bug in the default `segment by` calculation in compression.

**Thanks**

## 2.15.3 (2024-07-02)

This release contains bug fixes since the 2.15.2 release.
Expand Down
8 changes: 5 additions & 3 deletions sql/CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,12 @@ set(MOD_FILES
updates/2.14.2--2.15.0.sql
updates/2.15.0--2.15.1.sql
updates/2.15.1--2.15.2.sql
updates/2.15.2--2.15.3.sql)
updates/2.15.2--2.15.3.sql
updates/2.15.3--2.16.0.sql)

# The downgrade file to generate a downgrade script for the current version, as
# specified in version.config
set(CURRENT_REV_FILE reverse-dev.sql)
set(CURRENT_REV_FILE 2.16.0--2.15.3.sql)
# Files for generating old downgrade scripts. This should only include files for
# downgrade from one version to its previous version since we do not support
# skipping versions when downgrading.
Expand Down Expand Up @@ -80,7 +81,8 @@ set(OLD_REV_FILES
2.15.0--2.14.2.sql
2.15.1--2.15.0.sql
2.15.2--2.15.1.sql
2.15.3--2.15.2.sql)
2.15.3--2.15.2.sql
2.16.0--2.15.3.sql)

set(MODULE_PATHNAME "$libdir/timescaledb-${PROJECT_VERSION_MOD}")
set(LOADER_PATHNAME "$libdir/timescaledb")
Expand Down
67 changes: 67 additions & 0 deletions sql/updates/2.15.3--2.16.0.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
-- Enable tracking of statistics on a column of a hypertable.
--
-- hypertable - OID of the table to which the column belongs to
-- column_name - The column to track statistics for
-- if_not_exists - If set, and the entry already exists, generate a notice instead of an error
CREATE FUNCTION @extschema@.enable_column_stats(
hypertable REGCLASS,
column_name NAME,
if_not_exists BOOLEAN = FALSE
) RETURNS TABLE(column_stats_id INT, enabled BOOL)
AS '@MODULE_PATHNAME@', 'ts_chunk_column_stats_enable' LANGUAGE C VOLATILE;

-- Disable tracking of statistics on a column of a hypertable.
--
-- hypertable - OID of the table to remove from
-- column_name - NAME of the column on which the stats are tracked
-- if_not_exists - If set, and the entry does not exist,
-- generate a notice instead of an error
CREATE FUNCTION @extschema@.disable_column_stats(
hypertable REGCLASS,
column_name NAME,
if_not_exists BOOLEAN = FALSE
) RETURNS TABLE(hypertable_id INT, column_name NAME, disabled BOOL)
AS '@MODULE_PATHNAME@', 'ts_chunk_column_stats_disable' LANGUAGE C VOLATILE;

-- Track statistics for columns of chunks from a hypertable.
-- Currently, we track the min/max range for a given column across chunks.
-- More statistics (like bloom filters) will be added in the future.
--
-- A "special" entry for a column with invalid chunk_id, PG_INT64_MAX,
-- PG_INT64_MIN indicates that min/max ranges could be computed for this column
-- for chunks.
--
-- The ranges can overlap across chunks. The values could be out-of-date if
-- modifications/changes occur in the corresponding chunk and such entries
-- should be marked as "invalid" to ensure that the chunk is in
-- appropriate state to be able to use these values. Thus these entries
-- are different from dimension_slice which is used for tracking partitioning
-- column ranges which have different characteristics.
--
-- Currently this catalog supports datatypes like INT, SERIAL, BIGSERIAL,
-- DATE, TIMESTAMP etc. by storing the ranges in bigint columns. In the
-- future, we could support additional datatypes (which support btree style
-- >, <, = comparators) by storing their textual representation.
--
CREATE TABLE _timescaledb_catalog.chunk_column_stats (
id serial NOT NULL,
hypertable_id integer NOT NULL,
chunk_id integer NOT NULL,
column_name name NOT NULL,
range_start bigint NOT NULL,
range_end bigint NOT NULL,
valid boolean NOT NULL,
-- table constraints
CONSTRAINT chunk_column_stats_pkey PRIMARY KEY (id),
CONSTRAINT chunk_column_stats_ht_id_chunk_id_colname_key UNIQUE (hypertable_id, chunk_id, column_name),
CONSTRAINT chunk_column_stats_range_check CHECK (range_start <= range_end),
CONSTRAINT chunk_column_stats_hypertable_id_fkey FOREIGN KEY (hypertable_id) REFERENCES _timescaledb_catalog.hypertable (id),
CONSTRAINT chunk_column_stats_chunk_id_fkey FOREIGN KEY (chunk_id) REFERENCES _timescaledb_catalog.chunk (id)
);

SELECT pg_catalog.pg_extension_config_dump('_timescaledb_catalog.chunk_column_stats', '');

SELECT pg_catalog.pg_extension_config_dump(pg_get_serial_sequence('_timescaledb_catalog.chunk_column_stats', 'id'), '');

GRANT SELECT ON _timescaledb_catalog.chunk_column_stats TO PUBLIC;
GRANT SELECT ON _timescaledb_catalog.chunk_column_stats_id_seq TO PUBLIC;
7 changes: 7 additions & 0 deletions sql/updates/2.16.0--2.15.3.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
DROP FUNCTION IF EXISTS _timescaledb_functions.cagg_get_bucket_function_info(INTEGER);
-- remove chunk column statistics related objects
DROP FUNCTION IF EXISTS @extschema@.enable_column_stats(REGCLASS, NAME, BOOLEAN);
DROP FUNCTION IF EXISTS @extschema@.disable_column_stats(REGCLASS, NAME, BOOLEAN);
ALTER EXTENSION timescaledb DROP TABLE _timescaledb_catalog.chunk_column_stats;
ALTER EXTENSION timescaledb DROP SEQUENCE _timescaledb_catalog.chunk_column_stats_id_seq;
DROP TABLE IF EXISTS _timescaledb_catalog.chunk_column_stats;
67 changes: 0 additions & 67 deletions sql/updates/latest-dev.sql
Original file line number Diff line number Diff line change
@@ -1,67 +0,0 @@
-- Enable tracking of statistics on a column of a hypertable.
--
-- hypertable - OID of the table to which the column belongs to
-- column_name - The column to track statistics for
-- if_not_exists - If set, and the entry already exists, generate a notice instead of an error
CREATE FUNCTION @extschema@.enable_column_stats(
hypertable REGCLASS,
column_name NAME,
if_not_exists BOOLEAN = FALSE
) RETURNS TABLE(column_stats_id INT, enabled BOOL)
AS '@MODULE_PATHNAME@', 'ts_chunk_column_stats_enable' LANGUAGE C VOLATILE;

-- Disable tracking of statistics on a column of a hypertable.
--
-- hypertable - OID of the table to remove from
-- column_name - NAME of the column on which the stats are tracked
-- if_not_exists - If set, and the entry does not exist,
-- generate a notice instead of an error
CREATE FUNCTION @extschema@.disable_column_stats(
hypertable REGCLASS,
column_name NAME,
if_not_exists BOOLEAN = FALSE
) RETURNS TABLE(hypertable_id INT, column_name NAME, disabled BOOL)
AS '@MODULE_PATHNAME@', 'ts_chunk_column_stats_disable' LANGUAGE C VOLATILE;

-- Track statistics for columns of chunks from a hypertable.
-- Currently, we track the min/max range for a given column across chunks.
-- More statistics (like bloom filters) will be added in the future.
--
-- A "special" entry for a column with invalid chunk_id, PG_INT64_MAX,
-- PG_INT64_MIN indicates that min/max ranges could be computed for this column
-- for chunks.
--
-- The ranges can overlap across chunks. The values could be out-of-date if
-- modifications/changes occur in the corresponding chunk and such entries
-- should be marked as "invalid" to ensure that the chunk is in
-- appropriate state to be able to use these values. Thus these entries
-- are different from dimension_slice which is used for tracking partitioning
-- column ranges which have different characteristics.
--
-- Currently this catalog supports datatypes like INT, SERIAL, BIGSERIAL,
-- DATE, TIMESTAMP etc. by storing the ranges in bigint columns. In the
-- future, we could support additional datatypes (which support btree style
-- >, <, = comparators) by storing their textual representation.
--
CREATE TABLE _timescaledb_catalog.chunk_column_stats (
id serial NOT NULL,
hypertable_id integer NOT NULL,
chunk_id integer NOT NULL,
column_name name NOT NULL,
range_start bigint NOT NULL,
range_end bigint NOT NULL,
valid boolean NOT NULL,
-- table constraints
CONSTRAINT chunk_column_stats_pkey PRIMARY KEY (id),
CONSTRAINT chunk_column_stats_ht_id_chunk_id_colname_key UNIQUE (hypertable_id, chunk_id, column_name),
CONSTRAINT chunk_column_stats_range_check CHECK (range_start <= range_end),
CONSTRAINT chunk_column_stats_hypertable_id_fkey FOREIGN KEY (hypertable_id) REFERENCES _timescaledb_catalog.hypertable (id),
CONSTRAINT chunk_column_stats_chunk_id_fkey FOREIGN KEY (chunk_id) REFERENCES _timescaledb_catalog.chunk (id)
);

SELECT pg_catalog.pg_extension_config_dump('_timescaledb_catalog.chunk_column_stats', '');

SELECT pg_catalog.pg_extension_config_dump(pg_get_serial_sequence('_timescaledb_catalog.chunk_column_stats', 'id'), '');

GRANT SELECT ON _timescaledb_catalog.chunk_column_stats TO PUBLIC;
GRANT SELECT ON _timescaledb_catalog.chunk_column_stats_id_seq TO PUBLIC;
7 changes: 0 additions & 7 deletions sql/updates/reverse-dev.sql
Original file line number Diff line number Diff line change
@@ -1,7 +0,0 @@
DROP FUNCTION IF EXISTS _timescaledb_functions.cagg_get_bucket_function_info(INTEGER);
-- remove chunk column statistics related objects
DROP FUNCTION IF EXISTS @extschema@.enable_column_stats(REGCLASS, NAME, BOOLEAN);
DROP FUNCTION IF EXISTS @extschema@.disable_column_stats(REGCLASS, NAME, BOOLEAN);
ALTER EXTENSION timescaledb DROP TABLE _timescaledb_catalog.chunk_column_stats;
ALTER EXTENSION timescaledb DROP SEQUENCE _timescaledb_catalog.chunk_column_stats_id_seq;
DROP TABLE IF EXISTS _timescaledb_catalog.chunk_column_stats;
2 changes: 1 addition & 1 deletion version.config
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
version = 2.16.0-dev
version = 2.16.0
update_from_version = 2.15.3
downgrade_to_version = 2.15.3
Loading