News for hackers. Stuff that matters.
Re:Costs of a PostgreSQL connection by robbles on Wednesday February 19, 2014 @02:26PM (#7265621)
If pgbouncer makes this big a difference to performance, is it included in managed PostgreSQL services, such as Amazon RDS and Heroku Postgres?

Or would you have to roll your own pgbouncer setup for these systems?

Re:Costs of a PostgreSQL connection by _hans_ on Wednesday February 19, 2014 @02:37PM (#7265693)
Neither AWS RDS PostgreSQL nor Heroku has a PGBouncer.
Re:Costs of a PostgreSQL connection by btown on Wednesday February 19, 2014 @02:41PM (#7265716)
Re:Costs of a PostgreSQL connection by robbles on Wednesday February 19, 2014 @02:45PM (#7265749)
Saw that reference in the linked post from Heroku in the original article.

Has anyone used this? Is it configurable, or do they just choose some reasonable defaults?

Re:Costs of a PostgreSQL connection by thruflo on Wednesday February 19, 2014 @03:35PM (#7266050)
Works great for me. There's some minimal configuration explained in the pgbouncer docs. What the pgbouncer buildpack does is just route your DATABASE_URL through the local pgbouncer.

In my python app, I switched from an sqlalchemy connection pool per process (eg per gunicorn worker) to using a Null pool everwhere. No increase in latency; far fewer connections needed.