-
Notifications
You must be signed in to change notification settings - Fork 885
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]: Refreshing C-Agg with timezone (manually or by job) results in (ERROR: timestamp out of range) if start_offset is NULL. (also reproducible when start_offset and end_offset, both are null) #5474
Comments
I'm seeing the same, just when calling Inserting a single row into the hyper table allows creating all the continuous aggregates to succeed, but it means that I am unable to dump & restore the schema |
When refreshing from the beginning (window_start=NULL) of a Continuous Aggregate with variable time bucket we were getting a `timestamp out of range` error. Fixed it by setting `-Infinity` when passing `window_start=NULL` when refreshing a Continuous Aggregate with variable time bucket. Fixes timescale#5474, timescale#5534
When refreshing from the beginning (window_start=NULL) of a Continuous Aggregate with variable time bucket we were getting a `timestamp out of range` error. Fixed it by setting `-Infinity` when passing `window_start=NULL` when refreshing a Continuous Aggregate with variable time bucket. Fixes timescale#5474, timescale#5534
When refreshing from the beginning (window_start=NULL) of a Continuous Aggregate with variable time bucket we were getting a `timestamp out of range` error. Fixed it by setting `-Infinity` when passing `window_start=NULL` when refreshing a Continuous Aggregate with variable time bucket. Fixes #5474, #5534
When refreshing from the beginning (window_start=NULL) of a Continuous Aggregate with variable time bucket we were getting a `timestamp out of range` error. Fixed it by setting `-Infinity` when passing `window_start=NULL` when refreshing a Continuous Aggregate with variable time bucket. Fixes timescale#5474, timescale#5534 (cherry picked from commit f6c8468)
When refreshing from the beginning (window_start=NULL) of a Continuous Aggregate with variable time bucket we were getting a `timestamp out of range` error. Fixed it by setting `-Infinity` when passing `window_start=NULL` when refreshing a Continuous Aggregate with variable time bucket. Fixes #5474, #5534 (cherry picked from commit f6c8468)
Hello Team, I've noticed the recurrence of this error in tsdb version 2.13. This can be reproduced with the steps shared by @hardikm10. |
@yadhupk thank you for reporting that this is still an issue. I'll let our team working on continuous aggregates take a look. |
@erimatnor Do we have a progress status update by any chance? |
@dariogit-bit it was fixed in #6660 and will be part of the upcoming 2.14.2 |
I am having the same (or at least similar) issue.
Update to Adding |
Hello @hardikm10, I was able to reproduce the issue with TimescaleDB 2.14.2 and our latest development version (9f2d4e9). The |
The CAgg refresh job did not handle the NULL value of start_offset for a time_bucket function with a variable width properly. This problem has led to the creation of invalid invalidation records and 'timestamp out of range' errors during the next refresh. Fixes: timescale#5474
The CAgg refresh job did not handle the NULL value of start_offset for a time_bucket function with a variable width properly. This problem has led to the creation of invalid invalidation records and 'timestamp out of range' errors during the next refresh. Fixes: timescale#5474
The CAgg refresh job did not handle the NULL value of start_offset for a time_bucket function with a variable width properly. This problem has led to the creation of invalid invalidation records and 'timestamp out of range' errors during the next refresh. Fixes: timescale#5474
@jnidzwetzki Thank you, Jan! |
The CAgg refresh job did not handle the NULL value of start_offset for a time_bucket function with a variable width properly. This problem has led to the creation of invalid invalidation records and 'timestamp out of range' errors during the next refresh. Fixes: #5474
What type of bug is this?
Unexpected error
What subsystems and features are affected?
Continuous aggregate
What happened?
Refreshing C-Agg with timezone (manually or by job) results in (ERROR: timestamp out of range) if start_offset is NULL.
The reproducable instructions are attached below. few observations I wanted to add:
TimescaleDB version affected
2.10.1
PostgreSQL version used
PostgreSQL 15.2
What operating system did you use?
Timescale Cloud
What installation method did you use?
Other
What platform did you run on?
Timescale Cloud
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: