10

Django 1.6 introduces a Persistent Connections feature. However I've noticed that exiting a script that uses django's ORM leaves at least some of the connections open on the db side.
Setup: django 1.6.0, postgres 9.2 and psycopg2 2.5.1.

How do you gracefully close the connection to the database from a script?

The caveats section mentions that django opens a connection per thread, so in a multi-threaded script, does django create a connection per thread, even for threads that do not access the db?
Does each thread need to close the db connection separately?

If the answer to both questions above is yes, what can you do with daemon threads (e.g. for comm) which do not join on script exit?

Mohammed Shareef C
  • 3,829
  • 25
  • 35
Jonathan Livni
  • 101,334
  • 104
  • 266
  • 359
  • 1
    Hi, I'm using a similar setup and having the same issues of dandling connections. Have you found a solution for this problem? – user1102018 Jul 16 '14 at 08:25

2 Answers2

11

I ran into the same issue just now...

Solved it by calling the following code when my thread exits:

from django.db import close_old_connections
close_old_connections()
Johan De Taeye
  • 111
  • 2
7

I just upgraded and had this come up and close_old_connections in the main process before launching the sub processes does not work like the old close_connections did to give each process their own connection. But if you looked at what close_connections use to do you can recreate it docs.

So I do this in my main process before creating my sub processes.

from django.db import connections
for conn in connections.all():
    conn.close()

And it works great. The new close_old_connections will only close the connection if it has expired or has gone away.

byoungb
  • 1,771
  • 20
  • 31