-
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]: if_not_exists optional parameter for add_continuous_aggregate_policy() doesn't return notice if policy already exists #5688
Labels
Comments
Hi @ccrotty , Thanks for reporting this issue! Steps to reproduce:
|
Hi @shhnwz Any update on this bugfix? We are also experiencing the same issue. |
Also experiencing the same issue. Any update @shhnwz ? |
+1 here also |
Please upvote the issue if it affects you. It helps with prioritizing bugs. |
konskov
added a commit
to konskov/timescaledb
that referenced
this issue
Jan 16, 2024
konskov
added a commit
to konskov/timescaledb
that referenced
this issue
Jan 16, 2024
konskov
added a commit
to konskov/timescaledb
that referenced
this issue
Jan 16, 2024
konskov
added a commit
to konskov/timescaledb
that referenced
this issue
Jan 16, 2024
konskov
added a commit
to konskov/timescaledb
that referenced
this issue
Jan 17, 2024
konskov
added a commit
that referenced
this issue
Jan 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of bug is this?
Unexpected error
What subsystems and features are affected?
Continuous aggregate, Policy
What happened?
Executing the following when the continuous aggregate policy already exists returns an error instead of the expected NOTICE response:
SELECT add_continuous_aggregate_policy('tsmetrics.test_agg_mv', start_offset => null, end_offset => INTERVAL '1 hour', schedule_interval => INTERVAL '1 hour', if_not_exists => TRUE);
Error response was
ERROR: could not find start_offset in config for job SQL state: XX000
TimescaleDB version affected
2.9.3
PostgreSQL version used
14.6
What operating system did you use?
x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
What installation method did you use?
Docker
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
Create a continuous aggregate policy request with add_continuous_aggregate_policy() including the if_not_exists optional parameter. Then run the same request after it has been created.
The text was updated successfully, but these errors were encountered: