You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One workaround I know of is to insert a single tuple in that time range and then immediately delete it, you will have the chunk created without any data in it.
Although it might work, not a clean solution I think. Since merging of compressed chunks is coming to 2.19, I think this issue need to be resolved properly. This is the purpose of the issue opened after talking with Freedman
I agree, that's why I said its a known limitation. Can't speak for the plans on improvements but it should be fixed in the future (since we are aware of it).
Just offering you a workaround while the improvement comes.
What type of bug is this?
Other
What subsystems and features are affected?
Other
What happened?
I have two chunks with range start, range end. Hypertable range interval is set to 180 days
When I try to merge them I get
cannot create new chunk partition boundaries
TimescaleDB version affected
2.18.2
PostgreSQL version used
16.8
What operating system did you use?
Ubuntu 24.04.1
What installation method did you use?
Deb/Apt
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: