title: How do you know if PGBouncer is working?
body: <p>I've set up PGBouncer and configured it to connect to my postgres DB and it all connects just fine, however I'm not sure if its actually working.</p>
  
  <p>I have a php script that runs as a daemon and picks up beanstalk jobs. The problem is for every distinct user/action on the system it opens a new connection to postgres and then leaves that connection idling because the daemon doesn't actually stop running so the connection is never terminated (a quick fix for this was to reset the connection at the end of the script loop, but that is going to be inefficient with many connects).</p>
  
  <p>Anyway, this caused postgres to eventually run out of connections and lock up...</p>
  
  <p>So PGBouncer seems like the answer.</p>
  
  <p>But now when I run it, I see the same db connection multiple times when i do ps ax | grep postgres.</p>
  
  <p>Isn't PGBouncer supposed to only ever have 1 connection open to the DB and route all traffic through that connection? Then open a new connection if that one is full?</p>
  
  <p>At present I have 3 for one db connection (my access control system) and 2 for the other database (my client specific data).</p>
  
  <p>To me, it feels like if I roll out these changes then I will just be faced with the same problem that the connections will just get eaten up again because they're not being released.</p>
  
  <p>I hope that explains enough for someone to offer any advice.</p>