I was wondering why Django does not generate an SQL migration statement with the CONCURRENTLY keyword directly.
I have found a recent discussion about it on the GitHub project: https://github.com/django/django/pull/10901
I’ve seen this PR. It essentally does the same thing described in the article, but using a custom migration command.
I feel the problem with this approach is that