New install hangs on 0012 migration

[edmenendez]

Describe the bug
When trying to run python manage.py migrate it gets stuck on oauth2_provider.0012_add_token_checksum

To Reproduce
Run python manage.py migrate the first time. It will get through all the migrations except 0012 where it gets stuck.

Expected behavior
Complete run of all the migrations and an "OK" after running 0012.

Version
3.0.1

• I have tested with the latest published release and it's still a problem.
• I have tested with the master branch and it's still a problem.

Additional context
Checking locks in postgres, I can see that the DROP INDEX IF EXISTS seems to be blocking the rest of the migration.

"pid","usename","state","query_start","query"
42784,"django","idle in transaction","2025-08-11 16:43:19.601059-06","DROP INDEX IF EXISTS ""oauth2_provider_accesstoken_token_8af090f8_like"""
44744,"django","active","2025-08-11 16:43:19.688369-06","SELECT ""oauth2_provider_accesstoken"".""id"", ""oauth2_provider_accesstoken"".""token"", ""oauth2_provider_accesstoken"".""expires"", ""oauth2_provider_accesstoken"".""scope"", ""oauth2_provider_accesstoken"".""application_id"", ""oauth2_provider_accesstoken"".""user_id"", ""oauth2_provider_accesstoken"".""created"", ""oauth2_provider_accesstoken"".""updated"", ""oauth2_provider_accesstoken"".""source_refresh_token_id"", ""oauth2_provider_accesstoken"".""id_token_id"", ""oauth2_provider_accesstoken"".""token_checksum"" FROM ""oauth2_provider_accesstoken"""
44584,"postgres","active","2025-08-11 16:43:23.006766-06","SELECT pid, usename, state, query_start, query 
FROM pg_stat_activity 
WHERE state != 'idle' AND query LIKE '%oauth2_provider%'
ORDER BY query_start;"```

[edmenendez]

I copied the migrations to a place where I could edit it and modified settings.py to

MIGRATION_MODULES = {
    'oauth2_provider': 'core.oauth2_provider_migrations',
}

Then, I modified 0012 to remove migrations.RunPython(forwards_func, migrations.RunPython.noop) and I'm able to work around it.

[dopry]

@edmenendez what postgres version were you using?

[edmenendez]

PostgreSQL 13.21, compiled by Visual C++ build 1944, 64-bit

[dopry]

@n2ygk I was poking around in git and saw that you added the forward_func to migrations/0012_* in 1d19e54. This feels like it might be related. Would you have time to look into this?

[n2ygk]

@edmenendez can you check to see if perhaps you have a massive number of old access tokens (e.g. due to never cleaning up)?

Forward migration touches every "old" accesstoken.token which will cause the checksum to be computed.

See https://django-oauth-toolkit.readthedocs.io/en/latest/management_commands.html for cleartokens.

[edmenendez]

It's a brand new installation with 0 tokens.

[n2ygk]

Hmm, I'm at a loss. Can you turn on database debug logging? Something like this in settings:

DEBUG= True

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'filters': {
        'require_debug_true': {
            '()': 'django.utils.log.RequireDebugTrue',
        }
    },
    'formatters': {
        'verbose': {
        'format': '%(asctime)s %(levelname)s %(name)s.%(funcName)s:%(lineno)d: %(message)s'
        },
        'simple': {
            'format': '%(levelname)s %(message)s'
        },
    },
    'handlers': {
        'console': {
            'level': 'DEBUG',
            'filters': ['require_debug_true'],
            'class': 'logging.StreamHandler',
            'formatter': 'verbose'
        }
    },
    'loggers': {
        'django.db.backends': {
            'level': 'DEBUG',
            'handlers': ['console'],
        },
    }
}

[dopry]

@n2ygk just noticed 0d32dec, #1522 in our commit history. do you think that could be a fix? @edmenendez can you reproduce with master from git?

[n2ygk]

@n2ygk just noticed 0d32dec, #1522 in our commit history. do you think that could be a fix? @edmenendez can you reproduce with master from git?

That looks like a performance issue when there's a huge number of Access Tokens causing massive memory use whereas @edmenendez mentioned that his access token table was empty.

@edmenendez: Have you had a chance to turn on the database debugging I mentioned? Apologies for not "@"-ing you in that message.