We've got a Postgres DB on Win2003 Server that is the back end for
some web services (Django/Python). This results in connections being
opened and closed rapidly on the database. We don't have lots of
simultaneous connections and are ensuring that connections are closed
by the client correctly. Unfortunately, Windows, even though it marks
the connections as closed, seems to be leaving these connections
around for a while before cleaning them up. The result is that we end
up with tons of connections taking up resources and blocking new
connections once the connections settings limit is reached. They do
eventually get cleared up and transactions proceed but this is
obviously a capacity limiting issue.

Connection pooling (pgpool) doesn't seem to be an option under
Windows and the stateless nature of our app makes long lived
connections quite impractical. Is anyone else experiencing this issue?
Is there some Windows setting we can change to force it to clean up
after itself faster?

thanx,

-- Ben