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 DA4B7329F19 for ; Sun, 3 Oct 2004 14:27:26 +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 55660-10 for ; Sun, 3 Oct 2004 13:27:17 +0000 (GMT) Received: from boutiquenumerique.com (gailleton-2-82-67-9-10.fbx.proxad.net [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id C1F9F329F17 for ; Sun, 3 Oct 2004 14:27:17 +0100 (BST) Received: (qmail 5407 invoked from network); 3 Oct 2004 15:27:40 +0200 Received: from unknown (HELO musicbox) (192.168.0.2) by gailleton-2-82-67-9-10.fbx.proxad.net with SMTP; 3 Oct 2004 15:27:40 +0200 To: pgsql-performance@postgresql.org Subject: Re: Caching of Queries References: <00e801c4a4b6$5526dd30$8300a8c0@solent> <200410011010.40705.josh@agliodbs.com> <200410021304.21281.josh@agliodbs.com> Message-ID: Date: Sun, 03 Oct 2004 15:30:05 +0200 From: =?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?= Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/7.53 (Linux, build 737) 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/25 X-Sequence-Number: 8501 > If it was in pgpool or something similar, I could devote a separate > machine just for caching results leaving the db server untouched. BUT you would be limited to caching complete queries. There is a more efficient strategy...