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 6FFDD329F70 for ; Tue, 5 Oct 2004 16:35:46 +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 50932-04 for ; Tue, 5 Oct 2004 15:35:36 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 33790329CDD for ; Tue, 5 Oct 2004 16:35:35 +0100 (BST) Received: from solent (unknown [213.165.136.10]) by bayswater1.ymogen.net (Postfix) with ESMTP id A24ABA3405; Tue, 5 Oct 2004 16:35:28 +0100 (BST) Reply-To: From: "Matt Clark" To: "'Tatsuo Ishii'" Cc: , , , Subject: Re: Caching of Queries Date: Tue, 5 Oct 2004 16:35:28 +0100 Organization: Ymogen Ltd Message-ID: <012501c4aaf0$f12d0930$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <20041004.002823.85416338.t-ishii@sra.co.jp> 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/41 X-Sequence-Number: 8517 > I don't know what you are exactly referring to in above URL=20 > when you are talking about "potential pitfalls of pooling".=20 > 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'.