-
Notifications
You must be signed in to change notification settings - Fork 848
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
[Bug]: compress_chunk_time_interval does not work with BIGINT #6896
Comments
Yeah, I guess it's not possible to configure normally now, because the For the time being, I have a dumb workaround:
Just increase the interval 1000x, so that when it's converted to microseconds, you get the desired value in nanoseconds. |
What type of bug is this?
Configuration, Incorrect result
What subsystems and features are affected?
Compression
What happened?
if timestamp in a hypertable is a BIGINT, there is no way to use compress_chunk_time_interval https://docs.timescale.com/api/latest/compression/alter_table_compression/
I would expect to use
timescaledb.compress_chunk_time_interval = BIGINT
, but it does not work.TimescaleDB version affected
2.14.2
PostgreSQL version used
15.6
What operating system did you use?
What installation method did you use?
Not applicable
What platform did you run on?
Timescale Cloud
Relevant log output and stack trace
No response
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: