Apache::DBI caches database connection per process so you avoid the cost of creating a connection on each requests.
Pgbouncer pools database connections so that you don't tie up one postmaster process per httpd process. If you only have one webserver you may not have a real need for pgbouncer; it really is most useful when you have more httpd processes than you have postmaster processes. However you should be in the best position to grow using both. On Apr 22, 2014 7:03 AM, "jbiskofski" <jbiskof...@gmail.com> wrote: > I just want to confirm something with all you smart folks. > > I recently separated my web servers from my database servers, before I was > using Apache::DBI to maintain persistent connections between Apache and > Postgres. With this new setup I had to install PgBouncer. Can I now safely > remove Apache::DBI from my application and use regular DBI ?? > > Thank you. > >
