-
Notifications
You must be signed in to change notification settings - Fork 12
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
RAISE on zbx_drop_old_partitions #2
Comments
Change RAISE to RAISE NOTICE. |
The `zbx_drop_old_partitions` function was failing as the current partition would always be evaulated, was seen to expire in the future and would cause an exception to be raised. This logic is now only executed if the partion is actually scehduled for deletion.
Can you please try the fix in #3 in non-production? I don't have access to a test environment at the moment. |
@cavaliercoder, hello! Why this fix is still no in master? |
No-one has validated the fix in #3. I no longer have the means to test changes to this package and rely on feedback from users. |
I tested it. #3 is fix this issue. The old parts are deleted. But i did not test case when current partitions fell into the specified range. |
Hi Ryan,
First of all sorry if I'm bothering you and thanks for share these scripts :)
I have a problem with them and maybe you can give me a hand with a doubt. They work really well, but It fail in my environment dropping the old tables. This is an example of the execution, adding some debugging output.
It work correctly but when it go through the last table and execute the code to protect the current partition, It raise an error and I think that make a rollback, so doesn't drop any table. If I drop this part of code it works, but I’m really asking my self why this code doesn’t works in my environment but it does for yours.
Thanks in advance.
The text was updated successfully, but these errors were encountered: