#34839: OperationalError from Psycopg when using Connection Pool (Digital Ocean)
Django 4.2.3 psycopg 3.1.9
-------------------------------------+-------------------------------------
Reporter: Wes Garlock | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: postgresql, | Triage Stage:
psycopg, ORM | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
Thanks for this ticket. It's hard to say without a sample project, but
this is probably a duplicate of #24810 (check out also
[https://code.djangoproject.com/ticket/33297#comment:1 comment]).
--
Ticket URL: <https://code.djangoproject.com/ticket/34839#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a91b630a0-b3761fd9-456a-46ad-88dc-2a365af09181-000000%40eu-central-1.amazonses.com.
