Multi Threading Problem with Python + Django + PostgreSQL.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pradipbhosale
    New Member
    • Feb 2008
    • 3

    Multi Threading Problem with Python + Django + PostgreSQL.

    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(postgr es) 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(ope n/close)

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

    HELP ME OUT!!!!!
  • micmast
    New Member
    • Mar 2008
    • 144

    #2
    Do you close the connection when the thread terminates?
    Doesn't the connection timeout from the postgres side?

    Comment

    • pradipbhosale
      New Member
      • Feb 2008
      • 3

      #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.object s.get(Name = 'David Beckham');

      print obj_table.Name
      >> David Beckham

      So we never explicitly create any connection. So no question about closing it explicitly.

      Comment

      • micmast
        New Member
        • Mar 2008
        • 144

        #4
        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

        Comment

        Working...