SetTable fails race detector

The SetTable function is problematic if you have parallel go tests that spin up a new database and run the migrations on each individual one. It fails the go race detector as well. I'm forced to use a TestMain function to do this I guess, but what would you do if you want to set a different migration table in different parallel tests? Is there a particular reason it was chosen to make this essentially a mutable variable on the package itself as opposed to simply passing it as an option to Exec?

Start at SetTable and Exec, then reproduce the issue with parallel Go tests that create databases and run migrations under the race detector. Done means different parallel tests can use different migration tables without a data race; the payload does not name specific files or tests.