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

Repair relacl on extension upgrade #6290

Merged
merged 1 commit into from Nov 9, 2023
Merged

Conversation

mkindahl
Copy link
Contributor

@mkindahl mkindahl commented Nov 7, 2023

If users have accidentally been removed from pg_authid as a result of
bugs where dropping a user did not revoke privileges from all tables
where the had privileges, it will not be possible to create new chunks
since these require the user to be found when copying the privileges
for the parent table (either compressed hypertable or normal
hypertable).

To fix the situation, we repair the pg_class table when updating the
extension by modifying the relacl for relations and remove any user
that do not have an entry in pg_authid.

A repair function _timescaledb_functions.repair_relation_acls is
added that will perform the job. A makeaclitem from PG16 that accepts
a list of comma and used as part of the repair is also added as
_timescaledb_functions.makeaclitem.

@mkindahl mkindahl force-pushed the repair-relacl branch 6 times, most recently from c556592 to b9e0bb6 Compare November 7, 2023 14:04
Copy link

codecov bot commented Nov 7, 2023

Codecov Report

Merging #6290 (eca27a9) into main (ff88de9) will decrease coverage by 0.04%.
Report is 1 commits behind head on main.
The diff coverage is 82.85%.

@@            Coverage Diff             @@
##             main    #6290      +/-   ##
==========================================
- Coverage   65.40%   65.36%   -0.04%     
==========================================
  Files         247      247              
  Lines       57683    57672      -11     
  Branches    12828    12818      -10     
==========================================
- Hits        37726    37696      -30     
- Misses      18106    18121      +15     
- Partials     1851     1855       +4     
Files Coverage Δ
src/utils.c 61.40% <82.85%> (+1.08%) ⬆️

... and 17 files with indirect coverage changes

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

@mkindahl mkindahl force-pushed the repair-relacl branch 3 times, most recently from b70650c to cac77cb Compare November 7, 2023 18:01
@mkindahl mkindahl marked this pull request as ready for review November 7, 2023 20:39
Copy link

github-actions bot commented Nov 7, 2023

@konskov, @fabriziomello: please review this pull request.

Powered by pull-review

src/utils.c Outdated Show resolved Hide resolved
\z repair_test_int
\z repair_test_extra


Copy link
Member

Choose a reason for hiding this comment

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

Nit:

Suggested change

RETURNS AclItem AS '@MODULE_PATHNAME@', 'ts_makeaclitem'
LANGUAGE C STABLE PARALLEL SAFE;

-- Repair relations that have relacl entries for users that do not exist in pg_authid
Copy link
Member

Choose a reason for hiding this comment

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

I am wondering if we should keep this function exported and provide it to users. As you write in the commit, chunks can not be created if the ACLs are broken and it might be good to be able to call this function in these situations.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had that in the first version of the PR but have got comments before that we should not do that. I agree that it might be good to have a set of functions of this kind both for testing purposes and for helping users that end up in this situation in other ways.

@mkindahl
Copy link
Contributor Author

mkindahl commented Nov 8, 2023

@jnidzwetzki I added the alternative version as a separate commit. PTAL and see what you think.

@jnidzwetzki
Copy link
Member

@mkindahl I am more in favor of the new version and making _timescaledb_functions.repair_relation_acls available to users.

Copy link
Member

@jnidzwetzki jnidzwetzki left a comment

Choose a reason for hiding this comment

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

If we decide to keep the function exported, the PR title and the changelog entry should be adjusted.

@mkindahl mkindahl changed the title Repair relacl on upgrade Repair relacl on extension upgrade Nov 9, 2023
If users have accidentally been removed from `pg_authid` as a result of
bugs where dropping a user did not revoke privileges from all tables
where the had privileges, it will not be possible to create new chunks
since these require the user to be found when copying the privileges
for the parent table (either compressed hypertable or normal
hypertable).

To fix the situation, we repair the `pg_class` table when updating the
extension by modifying the `relacl` for relations and remove any user
that do not have an entry in `pg_authid`.

A repair function `_timescaledb_functions.repair_relation_acls` is
added that will perform the job. A `makeaclitem` from PG16 that accepts
a list of comma and used as part of the repair is also added as
`_timescaledb_functions.makeaclitem`.
@mkindahl mkindahl enabled auto-merge (rebase) November 9, 2023 08:28
@mkindahl mkindahl merged commit f231021 into timescale:main Nov 9, 2023
42 checks passed
@mkindahl mkindahl deleted the repair-relacl branch November 9, 2023 11:28
@mkindahl mkindahl added the bug label Nov 10, 2023
@timescale-automation
Copy link

Automated backport to 2.12.x not done: cherry-pick failed.

Git status

HEAD detached at origin/2.12.x
You are currently cherry-picking commit f2310216a.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .unreleased/fix_6290
	modified:   sql/maintenance_utils.sql
	modified:   sql/updates/post-update.sql
	modified:   src/utils.c
	new file:   test/expected/repair.out
	modified:   test/sql/CMakeLists.txt
	new file:   test/sql/repair.sql
	modified:   test/sql/updates/post.repair.sql
	modified:   test/sql/updates/setup.repair.sql
	modified:   tsl/test/shared/expected/extension.out

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   sql/updates/reverse-dev.sql


Job log

@timescale-automation timescale-automation added the auto-backport-not-done Automated backport of this PR has failed non-retriably (e.g. conflicts) label Nov 13, 2023
@jnidzwetzki jnidzwetzki mentioned this pull request Nov 23, 2023
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 23, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**

TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**Starting from TimescaleDB 2.13.0:**

* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 23, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**

TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**Starting from TimescaleDB 2.13.0:**

* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**

TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**Starting from TimescaleDB 2.13.0:**

* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**

TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0:**

* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0:**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* #5575 Add chunk-wise sorted paths for compressed chunks
* #5761 Simplify hypertable DDL API
* #5890 Reduce WAL activity by freezing compressed tuples immediately
* #6050 Vectorized aggregation execution for sum()
* #6062 Add metadata for chunk creation time
* #6077 Make Continous Aggregates materialized only (non-realtime) by default
* #6177 Change show_chunks/drop_chunks using chunk creation time
* #6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* #6185 Keep track of catalog version
* #6227 Use creation time in retention/compression policy
* #6307 Add SQL function cagg_validate_query

**Bugfixes**
* #6188 Add GUC for setting background worker log level
* #6222 Allow enabling compression on hypertable with unique expression index
* #6240 Check if worker registration succeeded
* #6254 Fix exception detail passing in compression_policy_execute
* #6264 Fix missing bms_del_member result assignment
* #6275 Fix negative bitmapset member not allowed in compression
* #6280 Potential data loss when compressing a table with a partial index that matches compression order.
* #6289 Add support for startup chunk exclusion with aggs
* #6290 Repair relacl on upgrade
* #6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* #6305 Make timescaledb_functions.makeaclitem strict
* #6332 Fix typmod and collation for segmentby columns
* #6339 Fix tablespace with constraints
* #6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit to jnidzwetzki/timescaledb that referenced this pull request Nov 27, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* timescale#5575 Add chunk-wise sorted paths for compressed chunks
* timescale#5761 Simplify hypertable DDL API
* timescale#5890 Reduce WAL activity by freezing compressed tuples immediately
* timescale#6050 Vectorized aggregation execution for sum()
* timescale#6062 Add metadata for chunk creation time
* timescale#6077 Make Continous Aggregates materialized only (non-realtime) by default
* timescale#6177 Change show_chunks/drop_chunks using chunk creation time
* timescale#6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* timescale#6185 Keep track of catalog version
* timescale#6227 Use creation time in retention/compression policy
* timescale#6307 Add SQL function cagg_validate_query

**Bugfixes**
* timescale#6188 Add GUC for setting background worker log level
* timescale#6222 Allow enabling compression on hypertable with unique expression index
* timescale#6240 Check if worker registration succeeded
* timescale#6254 Fix exception detail passing in compression_policy_execute
* timescale#6264 Fix missing bms_del_member result assignment
* timescale#6275 Fix negative bitmapset member not allowed in compression
* timescale#6280 Potential data loss when compressing a table with a partial index that matches compression order.
* timescale#6289 Add support for startup chunk exclusion with aggs
* timescale#6290 Repair relacl on upgrade
* timescale#6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* timescale#6305 Make timescaledb_functions.makeaclitem strict
* timescale#6332 Fix typmod and collation for segmentby columns
* timescale#6339 Fix tablespace with constraints
* timescale#6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
jnidzwetzki added a commit that referenced this pull request Nov 28, 2023
This release contains performance improvements, an improved hypertable DDL API
and bug fixes since the 2.12.2 release. We recommend that you upgrade at the next
available opportunity.

In addition, it includes these noteworthy features:

* Full PostgreSQL 16 support for all existing features
* Vectorized aggregation execution for sum()
* Track chunk creation time used in retention/compression policies

**Deprecation notice: Multi-node support**
TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
[here](docs/MultiNodeDeprecation.md).

If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).

**PostgreSQL 13 deprecation announcement**
We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will
announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be
included going forward.

**Starting from TimescaleDB 2.13.0**
* No Amazon Machine Images (AMI) are published. If you previously used AMI, please
use another [installation method](https://docs.timescale.com/self-hosted/latest/install/)
* Continuous Aggregates are materialized only (non-realtime) by default

**Features**
* #5575 Add chunk-wise sorted paths for compressed chunks
* #5761 Simplify hypertable DDL API
* #5890 Reduce WAL activity by freezing compressed tuples immediately
* #6050 Vectorized aggregation execution for sum()
* #6062 Add metadata for chunk creation time
* #6077 Make Continous Aggregates materialized only (non-realtime) by default
* #6177 Change show_chunks/drop_chunks using chunk creation time
* #6178 Show batches/tuples decompressed during DML operations in EXPLAIN output
* #6185 Keep track of catalog version
* #6227 Use creation time in retention/compression policy
* #6307 Add SQL function cagg_validate_query

**Bugfixes**
* #6188 Add GUC for setting background worker log level
* #6222 Allow enabling compression on hypertable with unique expression index
* #6240 Check if worker registration succeeded
* #6254 Fix exception detail passing in compression_policy_execute
* #6264 Fix missing bms_del_member result assignment
* #6275 Fix negative bitmapset member not allowed in compression
* #6280 Potential data loss when compressing a table with a partial index that matches compression order.
* #6289 Add support for startup chunk exclusion with aggs
* #6290 Repair relacl on upgrade
* #6297 Fix segfault when creating a cagg using a NULL width in time bucket function
* #6305 Make timescaledb_functions.makeaclitem strict
* #6332 Fix typmod and collation for segmentby columns
* #6339 Fix tablespace with constraints
* #6343 Enable segmentwise recompression in compression policy

**Thanks**
* @fetchezar for reporting an issue with compression policy error messages
* @jflambert for reporting the background worker log level issue
* @torazem for reporting an issue with compression and large oids
* @fetchezar for reporting an issue in the compression policy
* @lyp-bobi for reporting an issue with tablespace with constraints
* @pdipesh02 for contributing to the implementation of the metadata for chunk creation time,
             the generalized hypertable API, and show_chunks/drop_chunks using chunk creation time
* @lkshminarayanan for all his work on PG16 support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport-not-done Automated backport of this PR has failed non-retriably (e.g. conflicts) bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants