Release 2.12.0 #6086
Merged
Release 2.12.0 #6086
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@mahipv, @mkindahl: please review this pull request.
|
svenklemm
force-pushed
the
release_2.12.0
branch
2 times, most recently
from
027e119
to
06130a3
Compare
Codecov Report
@@ 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 |
svenklemm
force-pushed
the
release_2.12.0
branch
from
06130a3
to
1067065
Compare
jnidzwetzki
reviewed
Sep 18, 2023
iroussos
reviewed
Sep 18, 2023
jnidzwetzki
approved these changes
Sep 18, 2023
|
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. |
svenklemm
force-pushed
the
release_2.12.0
branch
from
1067065
to
c37bf95
Compare
|
Shouldn't we include PG12 deprecation? @iroussos, what would be a good one-liner for the release notes? |
iroussos
reviewed
Sep 19, 2023
svenklemm
force-pushed
the
release_2.12.0
branch
4 times, most recently
from
a67ce04
to
270ea4f
Compare
konskov
reviewed
Sep 20, 2023
konskov
approved these changes
Sep 20, 2023
iroussos
reviewed
Sep 20, 2023
svenklemm
force-pushed
the
release_2.12.0
branch
3 times, most recently
from
f81a171
to
d2ebc25
Compare
Only check files that were added, copied, modified or renamed in changelog check.
svenklemm
force-pushed
the
release_2.12.0
branch
from
d2ebc25
to
b00f2ed
Compare
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
svenklemm
force-pushed
the
release_2.12.0
branch
from
b00f2ed
to
4f985aa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
alter_job#5758 Enable altering job schedule type throughalter_jobset_chunk_time_intervalCAGGs aware #5852 Make set_chunk_time_interval CAggs awareBugfixes
Thanks
Disable-check: force-changelog-file
Disable-check: commit-count