Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity

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 (view raw or flat)
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

(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/ 

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2005-07-30 02:30:13
Subject: Re: current_schemas()
Previous:From: Alvaro HerreraDate: 2005-07-27 04:01:34
Subject: Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group