Dimitri Fontaine escribió: > A much better idea to solve this, in my opinion, would be to have > pgbouncer as a postmaster child, integrated into PostgreSQL. It allows > for choosing whether you want session pooling, transaction pooling or > statement pooling, which is a more deterministic way to choose when your > client connection will benefit from a fresh backend or an existing one. > And it's respecting some backend timeouts etc. Hmm. Seems like the best idea if we go this route would be one of Simon's which was to have better support for pluggable postmaster children. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
