title: Django ORM and PostgreSQL connection limits
body: <p>I'm running a Django project on Postgresql 8.1.21 (using Django 1.1.1, Python2.5, psycopg2, Apache2 with mod_wsgi 3.2). We've recently encountered this lovely error:</p>
  
  <p><code>OperationalError: FATAL:  connection limit exceeded for non-superusers</code></p>
  
  <p>I'm not the first person to run up against this. There's a lot of discussion about this error, specifically with psycopg, but much of it centers on older versions of Django and/or offer solutions involving edits to code in Django itself. I've yet to find a succinct explanation of how to solve the problem of the Django ORM (or psycopg, whichever is really responsible, in this case) leaving open Postgre connections.</p>
  
  <p>Will simply adding <code>connection.close()</code> at the end of every view solve this problem? Better yet, has anyone conclusively solved this problem and kicked this error's ass? </p>
  
  <p><strong>Edit</strong>: we later upped Postgresql's limit to 500 connections; this prevented the error from cropping up, but replaced it with excessive memory usage.</p>