"Joshua D. Drake" :
> Where pgbouncer might come in handy here, is that it can open more
> connections than you have httpd processes, and thus you will reduce
> the
> fork cost of the new process just because someone hits the website.
Unfortunatelly, ActiveRecords (Rails ORM) >= 3.1 is brok
On 02/25/2012 08:13 AM, Scott Ribe wrote:
What I'm trying to determine is: should I plan on using pgbouncer?
With Rails& Passenger, do the app server processes take and hold connections to
the db? Or take& release with queries/connections?
This is not a scalability question; given the traf
