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 288D532A265 for ; Fri, 1 Oct 2004 16:47:08 +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 49367-05 for ; Fri, 1 Oct 2004 15:47:03 +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 1846E32A259 for ; Fri, 1 Oct 2004 16:47:01 +0100 (BST) Received: from solent (unknown [213.165.136.10]) by bayswater1.ymogen.net (Postfix) with ESMTP id A49009EB62; Fri, 1 Oct 2004 16:46:59 +0100 (BST) Reply-To: From: "Matt Clark" To: "'Jim C. Nasby'" Cc: "'Postgresql Performance'" Subject: Re: Caching of Queries Date: Fri, 1 Oct 2004 16:46:59 +0100 Organization: Ymogen Ltd Message-ID: <012601c4a7cd$e358d300$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 In-Reply-To: <20041001151303.GU1297@decibel.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal 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/7 X-Sequence-Number: 8483 > OK, that'd work too... the point is if you're re-connecting=20 > all the time it doesn't really matter what else you do for=20 > performance. Yeah, although there is the chap who was asking questions on the list recently who had some very long-running code on his app servers, so was best off closing the connection because he had far too many postmaster processes just sitting there idle all the time! But you're right, it's a killer usually. M=20