#34914: Postgres connection is not restarted after it's dropped by the server,
even
if we use CONN_HEALTH_CHECKS=True
-------------------------------------+-------------------------------------
Reporter: Vitor Menegat | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by utkarshpandey12):
I am not executing raw sql instead I am using orm based queries.
Can I skip this line ?
{{{
with connection.cursor() as cursor:
cursor.execute("SELECT 1")
}}}
will a new connection be available from orm to make execute queries after
using close_old_connections() or anything else needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/34914#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d9db4f4a9-51945095-1658-4285-beb1-b57c90b88ebb-000000%40eu-central-1.amazonses.com.
