-
Notifications
You must be signed in to change notification settings - Fork 16
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
Max execution time #7
Comments
It makes sense. However, I guess it would be better to override SIGINT to stop pgcompact correctly, eg. wait for an ongoing query or process to finish, like the reindex one, instead of just breaking it in the middle, what might lead to unpleasant side effects like not dropped temporary indexes. So one could either safely Ctrl+C pgcompact or schedule Thoughts? |
I agree, that would be a much better option. We randomly encounter On Tue, Mar 31, 2015, 03:24 Sergey Konoplev [email protected]
|
Putting it down to my TODO then. BTW, pgcompact does not create temp tables, only indexes. |
Yeah, sorry, you are correct, only indices. On Tue, Mar 31, 2015, 11:58 Sergey Konoplev [email protected]
|
Since
pgcompact
is used as a database maintenance tool, you usually have a limited time when you can do maintenance (e.g. when there is less db activity), so it would be really nice if you could define a max execution time which would limit how long pgcompact can run. For example--max-execution-time=3600
which would limit execution to 1 hour.The text was updated successfully, but these errors were encountered: