--- Alvaro Herrera <[EMAIL PROTECTED]> escreveu: > > Hmm, seems a very similar thing can be had in Postgres by means of > pgpool. >
You're right. Using a JDBC connection pool to cache database connections, reuse physical connections and minimize expensive operations in the creation and closing of database sessions (1), or pgpool that is a connection pool server for PostgreSQL (2), the overhead of create a server process for each new connection almost disappears. It will only be necessary one connection pool for each database accessed, and pgpool will make a new connection if there's no user name and database name pair yet. Once more the middle tier simplifies the database operation. Regards, Halley (1) http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/9i_jdbc/OCIMidAuthSample/Readme.html (2) http://pgpool.projects.postgresql.org/ __________________________________________________ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
