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 062E9329EDF for ; Sat, 2 Oct 2004 21:02: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 64223-01 for ; Sat, 2 Oct 2004 20:02:41 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id CFAF4329EDA for ; Sat, 2 Oct 2004 21:02:40 +0100 (BST) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6448983; Sat, 02 Oct 2004 13:04:03 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Aaron Werman" Subject: Re: Caching of Queries Date: Sat, 2 Oct 2004 13:04:21 -0700 User-Agent: KMail/1.6.2 Cc: "Postgresql Performance" References: <00e801c4a4b6$5526dd30$8300a8c0@solent> <200410011010.40705.josh@agliodbs.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410021304.21281.josh@agliodbs.com> 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/15 X-Sequence-Number: 8491 Aaron, > I'm not sure I understand your req fully. I'm not surprised. I got wrapped up in an overly involved example and completely left off the points I was illustrating. So here's the points, in brief: 1) Query caching is not a single problem, but rather several different problems requiring several different solutions. 2) Of these several different solutions, any particular query result caching implementation (but particularly MySQL's) is rather limited in its applicability, partly due to the tradeoffs required. Per your explanation, Oracle has improved this by offering a number of configurable options. 3) Certain other caching problems would be solved in part by the ability to construct "in-memory" tables which would be non-durable and protected from cache-flushing. This is what I'm interested in chatting about. BTW, I AM using a summary table. -- --Josh Josh Berkus Aglio Database Solutions San Francisco