The migration lock is not released after terminating the migration about dbmate

[dossy]

Hi, @yegor86. It's not clear to me how this is a dbmate bug? dbmate itself does not acquire any metadata locks on its own when applying migrations on MySQL targets.

If you are using a new enough version of MySQL that supports online DDL, you could write your migration files to take advantage of it.

If you forcefully terminate dbmate's execution, then dbmate won't have an opportunity to gracefully clean up its connection to the server, and it is a long-standing behavior of MySQL to not terminate client queries upon network connection disconnection, requiring a DBA to kill the process from the server side if the process requires terminating.

I don't think there's anything that can be done by way of change to dbmate to address either of these things.

[dossy]

As everything described in this issue is either expected behavior, or something we cannot do anything about by a change to dbmate, I'm going to close this issue. If there's a proposal for a change to dbmate that could help here, please re-open this issue or open a new one outlining the change. Thanks!