X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 11A8D52B58 for ; Wed, 27 Jul 2005 09:35:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 36067-09 for ; Wed, 27 Jul 2005 12:35:07 +0000 (GMT) Received: from web52709.mail.yahoo.com (web52709.mail.yahoo.com [206.190.48.232]) by svr1.postgresql.org (Postfix) with SMTP id 2EEF452808 for ; Wed, 27 Jul 2005 09:35:06 -0300 (ADT) Received: (qmail 88243 invoked by uid 60001); 27 Jul 2005 12:35:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FmVm9u+E3QxWYrq5zD4GoqqOtI2jm4XAyYa01wLvYf/3Jnzo7wb2kapC4lUfkkUZX0M64t1EI1BNtAUU5hhOgw3xkHq0DsSMfB/rKDwQt3LSGKPbbNS9raqtn1Hpzgliyy3QefnW/zrNZP2hmu8M2KNZSM1kXW76mdeSE3KfobE= ; Message-ID: <20050727123509.88241.qmail@web52709.mail.yahoo.com> Received: from [201.8.20.32] by web52709.mail.yahoo.com via HTTP; Wed, 27 Jul 2005 09:35:09 ART Date: Wed, 27 Jul 2005 09:35:09 -0300 (ART) From: Halley Pacheco de Oliveira Subject: Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity To: pgsql-docs@postgresql.org Cc: Alvaro Herrera , Roman Neuhauser In-Reply-To: <20050727040134.GH20145@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.39 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200507/32 X-Sequence-Number: 3158 --- Alvaro Herrera 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/