Disallow hash partitioning on primary column #6993
Merged
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
nikkhils
added a commit
to nikkhils/timescaledb
that referenced
this pull request
Jun 4, 2024
The new "create_hypertable" API using the dimension info inadvertantly allowed creating hypertables with hash partitioning on the primary column. Since the rest of the machinery (policies, tiering, etc.) does not support hash partitions on primary column properly, we restrict it now in the new API. The older "create_hypertable" API was disallowing it earlier anyways. Fixes timescale#6993
The new "create_hypertable" API using the dimension info inadvertantly allowed creating hypertables with hash partitioning on the primary column. Since the rest of the machinery (policies, tiering, etc.) does not support hash partitions on primary column properly, we restrict it now in the new API. The older "create_hypertable" API was disallowing it earlier anyways. Fixes timescale#6993
fabriziomello
approved these changes
Jun 4, 2024
|
@nikkhils I think this should be part of 2.15.2, right? |
This was referenced Jun 5, 2024
Yup. Added the label. |
svenklemm
approved these changes
Jun 5, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Jun 5, 2024
The new "create_hypertable" API using the dimension info inadvertantly allowed creating hypertables with hash partitioning on the primary column. Since the rest of the machinery (policies, tiering, etc.) does not support hash partitions on primary column properly, we restrict it now in the new API. The older "create_hypertable" API was disallowing it earlier anyways. Fixes #6993 (cherry picked from commit 577b923)
timescale-automation
pushed a commit
that referenced
this pull request
Jun 5, 2024
The new "create_hypertable" API using the dimension info inadvertantly allowed creating hypertables with hash partitioning on the primary column. Since the rest of the machinery (policies, tiering, etc.) does not support hash partitions on primary column properly, we restrict it now in the new API. The older "create_hypertable" API was disallowing it earlier anyways. Fixes #6993 (cherry picked from commit 577b923)
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this pull request
Jun 6, 2024
This release contains performance improvements and bug fixes since the 2.15.0 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](https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql). For more details, see the following pull request [timescale#6797](timescale#6797). If you are migrating from TimescaleDB v2.15.0 or v2.15.1, no changes are required. **Bugfixes** * timescale#6975: Fix sort pushdown for partially compressed chunks. * timescale#6976: Fix removal of metadata function and update script. * timescale#6978: Fix segfault in compress_chunk with primary space partition. * timescale#6993: Disallow hash partitioning on primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting an issue with partially compressed chunks and ordering on joined columns.
Merged
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this pull request
Jun 6, 2024
This release contains performance improvements and bug fixes since the 2.15.0 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](https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql). For more details, see the following pull request [timescale#6797](timescale#6797). If you are migrating from TimescaleDB v2.15.0 or v2.15.1, no changes are required. **Bugfixes** * timescale#6975: Fix sort pushdown for partially compressed chunks. * timescale#6976: Fix removal of metadata function and update script. * timescale#6978: Fix segfault in compress_chunk with primary space partition. * timescale#6993: Disallow hash partitioning on primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting an issue with partially compressed chunks and ordering on joined columns.
pallavisontakke
added a commit
to pallavisontakke/timescaledb
that referenced
this pull request
Jun 7, 2024
This release contains performance improvements and bug fixes since the 2.15.1 release. Best practice is to upgrade at the next available opportunity. **Bugfixes** * timescale#6975: Fix sort pushdown for partially compressed chunks. * timescale#6976: Fix removal of metadata function and the update script. * timescale#6978: Fix segfault in compress_chunk with primary space partition. * timescale#6993: Disallow hash partitioning on the primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting the issue with partially compressed chunks and ordering on joined columns.
Merged
pallavisontakke
added a commit
that referenced
this pull request
Jun 7, 2024
This release contains bug fixes since the 2.15.1 release. Best practice is to upgrade at the next available opportunity. **Bugfixes** * #6975: Fix sort pushdown for partially compressed chunks. * #6976: Fix removal of metadata function and the update script. * #6978: Fix segfault in `compress_chunk` with primary space partition. * #6993: Disallow hash partitioning on the primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting the issue with partially compressed chunks and ordering on joined columns.
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this pull request
Jun 7, 2024
This release contains performance improvements and bug fixes since the 2.15.0 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](https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql). For more details, see the following pull request [timescale#6797](timescale#6797). If you are migrating from TimescaleDB v2.15.0 or v2.15.1, no changes are required. **Bugfixes** * timescale#6975: Fix sort pushdown for partially compressed chunks. * timescale#6976: Fix removal of metadata function and update script. * timescale#6978: Fix segfault in compress_chunk with primary space partition. * timescale#6993: Disallow hash partitioning on primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting an issue with partially compressed chunks and ordering on joined columns.
fabriziomello
added a commit
that referenced
this pull request
Jun 7, 2024
This release contains performance improvements and bug fixes since the 2.15.0 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](https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql). For more details, see the following pull request [#6797](#6797). If you are migrating from TimescaleDB v2.15.0 or v2.15.1, no changes are required. **Bugfixes** * #6975: Fix sort pushdown for partially compressed chunks. * #6976: Fix removal of metadata function and update script. * #6978: Fix segfault in compress_chunk with primary space partition. * #6993: Disallow hash partitioning on primary column. **Thanks** * @gugu for reporting the issue with catalog corruption due to update. * @srieding for reporting an issue with partially compressed chunks and ordering on joined columns.
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.
The new "create_hypertable" API using the dimension info inadvertantly allowed creating hypertables with hash partitioning on the primary column. Since the rest of the machinery (policies, tiering, etc.) does not support hash partitions on primary column properly, we restrict it now in the new API. The older "create_hypertable" API was disallowing it earlier anyways.