From: | Halley Pacheco de Oliveira <halleypo(at)yahoo(dot)com(dot)br> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
Subject: | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |
Date: | 2005-07-27 12:35:09 |
Message-ID: | 20050727123509.88241.qmail@web52709.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
--- Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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
(2) http://pgpool.projects.postgresql.org/
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-07-30 02:30:13 | Re: current_schemas() |
Previous Message | Alvaro Herrera | 2005-07-27 04:01:34 | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |