MG12 — DROP INDEX without CONCURRENTLY locks the table
Group: Migration safety · Auto-fixable: yes
Dropping an index without CONCURRENTLY takes an exclusive lock on the table for the duration of the drop. Use DROP INDEX CONCURRENTLY (outside a transaction block).
Example
Section titled “Example”bad: DROP INDEX idx;good: DROP INDEX CONCURRENTLY idx;Configure
Section titled “Configure”Disable this rule in banshee.toml:
[lint]exclude = ["MG12"]Or silence one line with -- noqa: MG12. See Linting.