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 2789C329E47 for ; Thu, 23 Sep 2004 10:14:52 +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 27521-08 for ; Thu, 23 Sep 2004 09:14:43 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 86A57329E4F for ; Thu, 23 Sep 2004 10:14:45 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i8N9Edfi032407 for ; Thu, 23 Sep 2004 09:14:42 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i8N8qPa6024583 for pgsql-performance@postgresql.org; Thu, 23 Sep 2004 08:52:25 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Caching of Queries Date: Thu, 23 Sep 2004 10:52:21 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 12 Message-ID: <41528EC5.8030901@bigfoot.com> References: <18410.1095883147@sss.pgh.pa.us> <1095905663.22485.294.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Neil Conway User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: <1095905663.22485.294.camel@localhost.localdomain> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org 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/233 X-Sequence-Number: 8361 Neil Conway wrote: > Another idea would be to improve the quality of the plan we generate at PREPARE time: > for instance you could generate 'n' plans for various combinations of > input parameters, and then choose the best query plan at EXECUTE time. > It's a difficult problem to solve, however (consider multiple parameters > to PREPARE, for example). Do you mean store different plans for each different histogram segment ? Regards Gaetano Mendola