Add an optional per-table lock timeout #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this commit, if a long (auto)vacuum or other lock was preventing Flexible Freeze from vacuuming a table, it would wait for that lock indefinitely, or until run_min minutes elapsed (if specified).
This commit addresses the problem by adding --lock-timeout, an optional flag for specifying the timeout (in milliseconds). If Flexible Freeze can't acquire a table lock after that amount of time, it gives up and moves on to the next table.