X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 01A243A4D8F for ; Mon, 24 Jan 2005 18:22:34 +0000 (GMT) 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 80286-09 for ; Mon, 24 Jan 2005 18:22:22 +0000 (GMT) Received: from quasar.skima.is (quasar.skima.is [212.30.200.205]) by svr1.postgresql.org (Postfix) with ESMTP id 01EC23A55B0 for ; Mon, 24 Jan 2005 18:22:22 +0000 (GMT) Received: from gnari ([157.157.193.37] [157.157.193.37]) by quasar.skima.is with ESMTP; Mon, 24 Jan 2005 18:22:13 Z Subject: Re: PgPool changes WAS: PostgreSQL clustering VS MySQL From: Ragnar =?ISO-8859-1?Q?Hafsta=F0?= To: Josh Berkus Cc: pgsql-performance@postgresql.org, Tatsuo Ishii In-Reply-To: <200501240952.40183.josh@agliodbs.com> References: <200501210947.53938.josh@agliodbs.com> <200501231442.52830.josh@agliodbs.com> <20050124.103033.21930526.t-ishii@sra.co.jp> <200501240952.40183.josh@agliodbs.com> Content-Type: text/plain Date: Mon, 24 Jan 2005 18:24:05 +0000 Message-Id: <1106591045.22635.7.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/443 X-Sequence-Number: 10133 On Mon, 2005-01-24 at 09:52 -0800, Josh Berkus wrote: > [about keeping connections open in web context] > Ah, clarity problem here. I'm talking about connection pooling tools from > the client (webserver) side, such as Apache::DBI, PHP's pg_pconnect, > Jakarta's connection pools, etc. Not pooling on the database server side, > which is what pgPool provides. note that these sometimes do not provide connection pooling as such, just persistent connections (Apache::DBI) > Most of these tools allocate a database connection to an HTTP/middleware > client, and only release it after a specific period of inactivity. This > means that you *could* count on "web-user==connection" for purposes of > switching back and forth to the master -- as long as the connection-recycling > timeout were set higher than the pgPool switch-off period. no. you can only count on web-server-process==connection, but not web-user==connection, unless you can garantee that the same user client always connects to same web-server process. am i missing something ? gnari