Open johnnymetz opened 2 months ago
It seems that in django 5.1, when using psycopg3, there is now support for using psycopg ConnectionPool directly, see this doc: https://docs.djangoproject.com/en/5.1/ref/databases/#connection-pool
Can you try setting pool as False?
"OPTIONS": {
"pool": False,
},
That didn't fix it unfortunately
Same error, on 4.0.6 all great but broken on 4.0.7
Confirming seeing the same issue on Django 5 and 4.0.7
Background
After upgrading from django-db-geventpool 4.0.6 to 4.0.7, I'm seeing an error when running the Django migrations in Django 5.1.
Steps to Reproduce
Requirements:
Database settings:
Run migrations:
Notes
django-db-geventpool==4.0.6
orDjango==5.0.8
fixes the bug