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 20996329EE9 for ; Thu, 7 Oct 2004 02:07:00 +0100 (BST) 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 08437-05 for ; Thu, 7 Oct 2004 01:06:52 +0000 (GMT) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by svr1.postgresql.org (Postfix) with ESMTP id 372FD329CD9 for ; Thu, 7 Oct 2004 02:06:54 +0100 (BST) Received: from srascb.sra.co.jp (srascb [133.137.8.65]) by sraigw.sra.co.jp (Postfix) with ESMTP id AD88062253; Thu, 7 Oct 2004 10:06:53 +0900 (JST) Received: from srascb.sra.co.jp (localhost [127.0.0.1]) by localhost.sra.co.jp (Postfix) with ESMTP id 9470B10CD06; Thu, 7 Oct 2004 10:06:53 +0900 (JST) Received: from sranhm.sra.co.jp (sranhm [133.137.44.16]) by srascb.sra.co.jp (Postfix) with ESMTP id 7513E10CD04; Thu, 7 Oct 2004 10:06:53 +0900 (JST) Received: from localhost (IDENT:t-ishii@hub-es6.sra.co.jp [133.137.44.7]) by sranhm.sra.co.jp (8.9.3+3.2W/3.7W-srambox) with ESMTP id KAA32531; Thu, 7 Oct 2004 10:06:53 +0900 Date: Thu, 07 Oct 2004 10:08:47 +0900 (JST) Message-Id: <20041007.100847.26272104.t-ishii@sra.co.jp> To: matt@ymogen.net Cc: pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com, pgsql-performance@postgresql.org Subject: Re: Caching of Queries From: Tatsuo Ishii In-Reply-To: <012501c4aaf0$f12d0930$8300a8c0@solent> References: <20041004.002823.85416338.t-ishii@sra.co.jp> <012501c4aaf0$f12d0930$8300a8c0@solent> X-Mailer: Mew version 2.3 on Emacs 20.7 / Mule 4.1 =?iso-2022-jp?B?KBskQjAqGyhCKQ==?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/74 X-Sequence-Number: 8550 > > I don't know what you are exactly referring to in above URL > > when you are talking about "potential pitfalls of pooling". > > Please explain more. > > Sorry, I wasn't implying that pgpool doesn't deal with the issues, just that > some people aren't necessarily aware of them up front. For instance, pgpool > does an 'abort transaction' and a 'reset all' in lieu of a full reconnect > (of course, since a full reconnect is exactly what we are trying to avoid). > Is this is enough to guarantee that a given pooled connection behaves > exactly as a non-pooled connection would from a client perspective? For > instance, temporary tables are usually dropped at the end of a session, so a > client (badly coded perhaps) that does not already use persistent > connections might be confused when the sequence 'connect, create temp table > foo ..., disconnect, connect, create temp table foo ...' results in the > error 'Relation 'foo' already exists'. First, it's not a particular problem with pgpool. As far as I know any connection pool solution has exactly the same problem. Second, it's easy to fix if PostgreSQL provides a functionarity such as:"drop all temporary tables if any". I think we should implement it if we agree that connection pooling should be implemented outside the PostgreSQL engine itself. I think cores agree with this. -- Tatsuo Ishii