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 6CBFB329CD9 for ; Wed, 22 Sep 2004 20:59:21 +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 11523-09 for ; Wed, 22 Sep 2004 19:59:13 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8B89A329E73 for ; Wed, 22 Sep 2004 20:59:14 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i8MJx7ZD018411; Wed, 22 Sep 2004 15:59:08 -0400 (EDT) To: Scott Kirkwood Cc: pgsql-performance@postgresql.org Subject: Re: Caching of Queries In-reply-to: References: Comments: In-reply-to Scott Kirkwood message dated "Wed, 22 Sep 2004 16:50:26 -0300" Date: Wed, 22 Sep 2004 15:59:07 -0400 Message-ID: <18410.1095883147@sss.pgh.pa.us> From: Tom Lane 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/222 X-Sequence-Number: 8350 Scott Kirkwood writes: > What do you think? I think this would allow the problems of cached plans to bite applications that were previously not subject to them :-(. An app that wants plan re-use can use PREPARE to identify the queries that are going to be re-executed. regards, tom lane