Home » Oreps » Timescaledb » All Releases » 2.15.3 Release

timescale/timescaledb

An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.

Watch

Basic Details Issues Addressed Top Contributors Directory Browser Release Notes

Timescaledb 2.15.3

Timescaledb: 2.15.3 Release

Release date:

July 2, 2024

Previous version:

2.15.2 (released June 7, 2024)

Magnitude:

3,167 Diff Delta

Contributors:

8 total committers

Data confidence:

Commits:

27 Features Released with 2.15.3

Browse Other Releases

Latest Pending Unreleased 😎

2.17.2 Released November 6, 2024

0 Δ

2.17.1 Released October 25, 2024

342 Δ

2.17.0 Released October 8, 2024

0 Δ

2.16.1 Released August 6, 2024

495 Δ

2.16.0 Released July 31, 2024

10,949 Δ

2.15.3 Released July 2, 2024

3,167 Δ

2.15.2 Released June 7, 2024

949 Δ

2.15.1 Released May 28, 2024

2,460 Δ

2.15.0 Released May 7, 2024

8,473 Δ

2.14.2 Released February 20, 2024

289 Δ

Top Contributors in 2.15.3

svenklemm

antekresic

fabriziomello

nikkhils

pallavisontakke

zilder

akuzm

mkindahl

Directory Browser for 2.15.3

We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.

Release Notes Published

This release contains bug fixes since the 2.15.2 release. Best practice is to upgrade at the next available opportunity.

Migrating from self-hosted TimescaleDB v2.14.x and earlier

After you run ALTER EXTENSION, you must run this SQL script. For more details, see the following pull request #6797.

If you are migrating from TimescaleDB v2.15.0, v2.15.1 or v2.15.2, no changes are required.

Bugfixes * #7061: Fix the handling of multiple unique indexes in a compressed INSERT. * #7080: Fix the corresponding equivalence member not found error. * #7088: Fix the leaks in the DML functions. * #7035: Fix the error when acquiring a tuple lock on the OSM chunks on the replica. * #7091: Fix ORDER BY/GROUP BY expression not found in targetlist on PG16

Thanks * @Kazmirchuk for reporting the issue about leaks with the functions in DML.