> Actually, it doesn't disconnect. It issues "RESET ALL;DISCARD ALL;" and > keeps the connection open, waiting for the next client transaction. It > only disconnects after a connection has been idle for a preset interval > (generally 5 minutes).
Ok. So if all clients are busy and keep on sending transactions, pgbouncer cannot lower down the number of connections to PostgreSQL, right? > > Question is, what > > does pgbouncer deal with session span data, such as temporary tables > > or datestyle set by SET command? > > It doesn't. You're specifically warned not to use these things if > you're running in Transaction mode. Ok. Also I guess in Transaction mode extended protocol cannot be used (i.e. Java cannot be used). -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
