By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,096 Members | 1,568 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,096 IT Pros & Developers. It's quick & easy.

Multi Threading Problem with Python + Django + PostgreSQL.

P: 3
Hello every body. I am new to this forum and also in Python.
Read many things about multi threading in python. But still having problem.

I am using Django Framework with Python having PostgreSQL as backend database with Linux OS. My applications are long running. I am using threading.
The problem I am facing is that the connections that are being created for database(postgres) update are not getting closed even though my threads had returned and updated database successfully. It is not like that the connections are not being reused. They r being reused but after sometime new one is created. Like this it creates too many connections and hence exceeding MAX_CONNECTION limit of postgres conf.

** I am using psycopg2 as adaptor for python to postgres connection. which itself handles the connections(open/close)

Now the problem is with Django / Python / psycopg2 or any thing else??

HELP ME OUT!!!!!
Mar 26 '08 #1
Share this Question
Share on Google+
3 Replies


micmast
100+
P: 144
Do you close the connection when the thread terminates?
Doesn't the connection timeout from the postgres side?
Mar 27 '08 #2

P: 3
Actualy the django itself manages connections through that pcycopg (correct me if i am wrong). I am not explicitly opening any database connection. The statements are like below in django . Suppose 'my_table' is name of table.

obj_table = my_table.objects.get(Name = 'David Beckham');

print obj_table.Name
>> David Beckham

So we never explicitly create any connection. So no question about closing it explicitly.
Mar 31 '08 #3

micmast
100+
P: 144
if you don't have anything to say about wether or not a connection has to be closed, maybe try to close it from the postgres side with a timeout value or something. if possible
Mar 31 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.