Change default for timescaledb.compress_truncate_behaviour to truncate_or_delete#9696
Open
Change default for timescaledb.compress_truncate_behaviour to truncate_or_delete#9696
Conversation
|
@pnthao, @dbeck: please review this pull request.
|
Poroma-Banerjee
approved these changes
Apr 29, 2026
…e_or_delete We want compression to not wait for the AccessExclusiveLock needed for TRUNCATE and instead fall back to DELETE when the lock cannot be acquired.
svenklemm
force-pushed
the
sven/compression_truncate
branch
from
8819e5b to
dfa6a5b
Compare
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
2 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.
We want compression to not wait for the AccessExclusiveLock needed for
TRUNCATE and instead fall back to DELETE when the lock cannot be
acquired.