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.12.0 #6086

Merged
merged 2 commits into from Sep 20, 2023
Merged

Release 2.12.0 #6086

merged 2 commits into from Sep 20, 2023

Conversation

svenklemm
Copy link
Member

@svenklemm svenklemm commented Sep 18, 2023

This release contains performance improvements for compressed hypertables
and continuous aggregates and bug fixes since the 2.11.2 release.
We recommend that you upgrade at the next available opportunity.

This release moves all internal functions from the _timescaleb_internal
schema into the _timescaledb_functions schema. This separates code from
internal data objects and improves security by allowing more restrictive
permissions for the code schema. If you are calling any of those internal
functions you should adjust your code as soon as possible. This version
also includes a compatibility layer that allows calling them in the old
location but that layer will be removed in 2.14.0.

PostgreSQL 12 support removal announcement
Following the deprecation announcement for PostgreSQL 12 in TimescaleDB 2.10,
PostgreSQL 12 is not supported starting with TimescaleDB 2.12.
Currently supported PostgreSQL major versions are 13, 14 and 15.
PostgreSQL 16 support will be added with a following TimescaleDB release.

Features

Bugfixes

Thanks

  • @ajcanterbury for reporting a problem with lateral joins on compressed chunks
  • @alexanderlaw for reporting multiple server crashes
  • @lukaskirner for reporting a bug with monthly continuous aggregates
  • @mrksngl for reporting a bug with unusual user names
  • @willsbit for reporting a crash in time_bucket_gapfill

Disable-check: force-changelog-file
Disable-check: commit-count

@github-actions
Copy link

@mahipv, @mkindahl: please review this pull request.

Powered by pull-review

@codecov
Copy link

codecov bot commented Sep 18, 2023

Codecov Report

Merging #6086 (4f985aa) into main (9dc699a) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #6086      +/-   ##
==========================================
- Coverage   81.51%   81.49%   -0.02%     
==========================================
  Files         246      246              
  Lines       56773    56727      -46     
  Branches    12587    12568      -19     
==========================================
- Hits        46276    46229      -47     
+ Misses       8114     8107       -7     
- Partials     2383     2391       +8     

see 19 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link

@iroussos iroussos left a comment

Choose a reason for hiding this comment

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

Thank you @svenklemm, I have added a few small comments

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@iroussos
Copy link

I don't see #6067 included - the updates required for Data Tiering GA is a major reason why we are having 2.12 a little bit earlier, so we should make sure that everything is included before tagging.

@svenklemm do you mind also making sure with @zilder, @gayyappan that this is the only one remaining and that there is nothing else we forgot to add to the 2.12 milestone?

@svenklemm
Copy link
Member Author

I don't see #6067 included - the updates required for Data Tiering GA is a major reason why we are having 2.12 a little bit earlier, so we should make sure that everything is included before tagging.

@svenklemm do you mind also making sure with @zilder, @gayyappan that this is the only one remaining and that there is nothing else we forgot to add to the 2.12 milestone?

#6067 has not been merged yet, will add it once its merged.

@horzsolt
Copy link

Shouldn't we include PG12 deprecation? @iroussos, what would be a good one-liner for the release notes?

CHANGELOG.md Show resolved Hide resolved
@svenklemm svenklemm force-pushed the release_2.12.0 branch 4 times, most recently from a67ce04 to 270ea4f Compare September 20, 2023 07:21
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@svenklemm svenklemm force-pushed the release_2.12.0 branch 3 times, most recently from f81a171 to d2ebc25 Compare September 20, 2023 08:24
Only check files that were added, copied, modified or renamed in
changelog check.
This release contains performance improvements for compressed hypertables
and continuous aggregates and bug fixes since the 2.11.2 release.
We recommend that you upgrade at the next available opportunity.

This release moves all internal functions from the _timescaleb_internal
schema into the _timescaledb_functions schema. This separates code from
internal data objects and improves security by allowing more restrictive
permissions for the code schema. If you are calling any of those internal
functions you should adjust your code as soon as possible. This version
also includes a compatibility layer that allows calling them in the old
location but that layer will be removed in 2.14.0.

**PostgreSQL 12 support removal announcement**
Following the deprecation announcement for PostgreSQL 12 in TimescaleDB 2.10,
PostgreSQL 12 is not supported starting with TimescaleDB 2.12.
Currently supported PostgreSQL major versions are 13, 14 and 15.
PostgreSQL 16 support will be added with a following TimescaleDB release.

**Features**
* timescale#5137 Insert into index during chunk compression
* timescale#5150 MERGE support on hypertables
* timescale#5515 Make hypertables support replica identity
* timescale#5586 Index scan support during UPDATE/DELETE on compressed hypertables
* timescale#5596 Support for partial aggregations at chunk level
* timescale#5599 Enable ChunkAppend for partially compressed chunks
* timescale#5655 Improve the number of parallel workers for decompression
* timescale#5758 Enable altering job schedule type through `alter_job`
* timescale#5805 Make logrepl markers for (partial) decompressions
* timescale#5809 Relax invalidation threshold table-level lock to row-level when refreshing a Continuous Aggregate
* timescale#5839 Support CAgg names in chunk_detailed_size
* timescale#5852 Make set_chunk_time_interval CAggs aware
* timescale#5868 Allow ALTER TABLE ... REPLICA IDENTITY (FULL|INDEX) on materialized hypertables (continuous aggregates)
* timescale#5875 Add job exit status and runtime to log
* timescale#5909 CREATE INDEX ONLY ON hypertable creates index on chunks

**Bugfixes**
* timescale#5860 Fix interval calculation for hierarchical CAggs
* timescale#5894 Check unique indexes when enabling compression
* timescale#5951 _timescaledb_internal.create_compressed_chunk doesn't account for existing uncompressed rows
* timescale#5988 Move functions to _timescaledb_functions schema
* timescale#5788 Chunk_create must add an existing table or fail
* timescale#5872 Fix duplicates on partially compressed chunk reads
* timescale#5918 Fix crash in COPY from program returning error
* timescale#5990 Place data in first/last function in correct mctx
* timescale#5991 Call eq_func correctly in time_bucket_gapfill
* timescale#6015 Correct row count in EXPLAIN ANALYZE INSERT .. ON CONFLICT output
* timescale#6035 Fix server crash on UPDATE of compressed chunk
* timescale#6044 Fix server crash when using duplicate segmentby column
* timescale#6045 Fix segfault in set_integer_now_func
* timescale#6053 Fix approximate_row_count for CAggs
* timescale#6081 Improve compressed DML datatype handling
* timescale#6084 Propagate parameter changes to decompress child nodes

**Thanks**
* @ajcanterbury for reporting a problem with lateral joins on compressed chunks
* @alexanderlaw for reporting multiple server crashes
* @lukaskirner for reporting a bug with monthly continuous aggregates
* @mrksngl for reporting a bug with unusual user names
* @willsbit for reporting a crash in time_bucket_gapfill
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants