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 EB5A3329CFB for ; Mon, 27 Sep 2004 15:19:17 +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 91400-01 for ; Mon, 27 Sep 2004 14:19:08 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 40301329EBB for ; Mon, 27 Sep 2004 15:19:10 +0100 (BST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i8REHuc28214; Mon, 27 Sep 2004 10:17:56 -0400 (EDT) From: Bruce Momjian Message-Id: <200409271417.i8REHuc28214@candle.pha.pa.us> Subject: Re: Caching of Queries In-Reply-To: To: Scott Kirkwood Date: Mon, 27 Sep 2004 10:17:56 -0400 (EDT) Cc: pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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: 200409/282 X-Sequence-Number: 8410 Added to TODO: * Consider automatic caching of queries at various levels: o Parsed query tree o Query execute plan o Query results --------------------------------------------------------------------------- Scott Kirkwood wrote: > On Mon, 27 Sep 2004 15:03:01 +1000, Neil Conway wrote: > > I think the conclusion of past discussions about this feature is that > > it's a bad idea. Last I checked, MySQL has to clear the *entire* query > > cache when a single DML statement modifying the table in question is > > issued. Not to mention that the feature is broken for non-deterministic > > queries (like now(), ORDER BY random(), or nextval('some_seq'), and so > > on). That makes the feature close to useless for a lot of situations, > > albeit not every situation. > > I think it's important to demark three levels of possible caching: > 1) Caching of the parsed query tree > 2) Caching of the query execute plan > 3) Caching of the query results > > I think caching the query results (3) is pretty dangerous and > difficult to do correctly. > > Caching of the the execute plan (2) is not dangerous but may actually > execute more slowly by caching a bad plan (i.e. a plan not suited to > the current data) > > Caching of the query tree (1) to me has very little downsides (except > extra coding). But may not have a lot of win either, depending how > much time/resources are required to parse the SQL and lookup the > objects in the system tables (something I've never gotten a > satisfactory answer about). Also, some of the query cache would have > to be cleared when DDL statements are performed. > > -Scott > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073