#1536 introduces inspection of performance_shcema.metadata_locks and this change is part of the https://github.com/github/gh-ost/releases/tag/v1.1.8-rc.
However this breaks migrations for for database instances with performance_schema turned off. Glad that #1616 is introduced to suppress metadata check but it's not included the 1.1.8-rc which kind of moot.
Is it possible to introduce a new release cut that includes suppression as well to unblock migrations for database that can't enable performance_schema?
If it's not a possibility, are there any nightly builds that I can use to overcome this friction?
#1536 introduces inspection of
performance_shcema.metadata_locks and this change is part of the https://github.com/github/gh-ost/releases/tag/v1.1.8-rc.However this breaks migrations for for database instances with performance_schema turned off. Glad that #1616 is introduced to suppress metadata check but it's not included the 1.1.8-rc which kind of moot.
Is it possible to introduce a new release cut that includes suppression as well to unblock migrations for database that can't enable performance_schema?
If it's not a possibility, are there any nightly builds that I can use to overcome this friction?