-
Notifications
You must be signed in to change notification settings - Fork 897
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]: cagg_migrate failed with "timestamp out of range" #5359
Comments
I was not able to reproduce it at first - but it turned out that I was just in luck; because the timezone was set to
repro: https://github.com/kgyrtkirk/reprox/tree/tsdb-8359-timestamp-out-of-range I'll add this to the backlog for further investigation. |
Don't know which version of Postgres you are using, but my version (v14) doesn't accept "C" value for timezone: set timezone=C;
invalid value for parameter "TimeZone": "c"
SET TIME ZONE 'UTC';
SET
Time: 0.002s
CALL cagg_migrate('farm_tscondition_10m', override => TRUE, drop_old => TRUE);
WARNING: refresh the continuous aggregate after the migration executing this statement: "CALL public.refresh_continuous_aggregate('public.farm_tscondition_10m', CAST('4714-11-24 00:00:00 BC' AS timestamp with time zone), NULL);" |
The CAgg migration path contained two bugs. This PR fixes both. A typo in the column type prevented 'timestamp with time zone' buckets from being handled properly. In addition, a custom setting of the datestyle could create errors during the parsing of the generated timestamp values. Fixes: timescale#5359
The CAgg migration path contained two bugs. This PR fixes both. A typo in the column type prevented 'timestamp with time zone' buckets from being handled properly. In addition, a custom setting of the datestyle could create errors during the parsing of the generated timestamp values. Fixes: timescale#5359
The CAgg migration path contained two bugs. This PR fixes both. A typo in the column type prevented 'timestamp with time zone' buckets from being handled properly. In addition, a custom setting of the datestyle could create errors during the parsing of the generated timestamp values. Fixes: timescale#5359
The CAgg migration path contained two bugs. This PR fixes both. A typo in the column type prevented 'timestamp with time zone' buckets from being handled properly. In addition, a custom setting of the datestyle could create errors during the parsing of the generated timestamp values. Fixes: #5359
What type of bug is this?
Other
What subsystems and features are affected?
Continuous aggregate
What happened?
I'm migrating CAgg to new format and get "timestamp out of range" error.
Here is the copy of reproducible DB:
nanola-trungthao.zip
TimescaleDB version affected
2.10.0
PostgreSQL version used
14.6
What operating system did you use?
Ubuntu 22.04
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: