Analyze partitioned tables with lock retries
What does this MR do and why?
We need to manually analyze partitioned tables on a schedule to populate their statistics, but for busy tables the lock needed for analyze could take a while to be obtained and it causes long running transactions, like the previous incidents gitlab-com/gl-infra/production#18073 (closed)
In this case it was impossible to get the lock on p_ci_job_artifacts
and the query was killed after an hour by the statement timeout config.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.