Truncate constraint name before trying to rename - #10265
Merged
Merged
Conversation
|
@antekresic, @akuzm: please review this pull request.
|
svenklemm
added
the
force-auto-backport
Poroma-Banerjee
approved these changes
Jul 15, 2026
akuzm
approved these changes
Jul 15, 2026
alexeyklyukin
approved these changes
Jul 15, 2026
The check whether to rename a constraint would operate on the untruncated names which resulting in an error when the constraint name would be the same after truncation.
svenklemm
force-pushed
the
sven/truncated_names
branch
from
July 16, 2026 05:19
65d80c7 to
597aead
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merged
surister
pushed a commit
that referenced
this pull request
Jul 16, 2026
# TimescaleDB Changelog **Please note: When updating your database, you should connect using `psql` with the `-X` flag to prevent any `.psqlrc` commands from accidentally triggering the load of a previous TimescaleDB version.** ## 2.28.3 (2026-07-16) This release contains performance improvements and bug fixes since the 2.28.2 release. We recommend that you upgrade at the next available opportunity. **Bugfixes** * [#10082](#10082) Wrong result when evaluating a function returning `NULL` in the columnar query execution pipeline * [#10178](#10178) Fix incorrect usage of sort transformation for sort key expressions with negative constants * [#10179](#10179) Allow enabling and disabling triggers on hypertables with columnstore enabled * [#10182](#10182) Fix columnstore sort pushdown to check for different query sort key collation * [#10209](#10209) Fix potentially wrong results for `stddev(float4)` and `stddev(float8)` when used with `avg()` in the columnar query execution pipeline * [#10212](#10212) Fix race condition when enabling compression on a hypertable * [#10230](#10230) Batch filtering for compressed `DML` should respect collation * [#10254](#10254) Direct delete failed to handle array predicates with `NULL` values and deleted more rows than intended ([#10129](#10129)) * [#10257](#10257) Reuse existing `dimension_slice` IDs when possible * [#10265](#10265) Truncate constraint name before trying to rename **Thanks** * @juantxorena for reporting that triggers could not be enabled or disabled on hypertables with columnstore enabled
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 check whether to rename a constraint would operate on the
untruncated names which resulting in an error when the constraint
name would be the same after truncation.