X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C792DD1B438 for ; Thu, 11 Dec 2003 17:00:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 72502-05 for ; Thu, 11 Dec 2003 12:59:52 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id D6147D1B46E for ; Thu, 11 Dec 2003 12:59:51 -0400 (AST) 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 hBBGxobK005184 for ; Thu, 11 Dec 2003 16:59:51 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hBBGaZG5002490 for pgsql-performance@postgresql.org; Thu, 11 Dec 2003 16:36:35 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: hints in Postgres? Date: Thu, 11 Dec 2003 11:31:45 -0500 Organization: cbbrowne Computing Inc Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:y+0IPFvfAM3U+PlNhp3qRQc1Qx0= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/182 X-Sequence-Number: 5042 Quoth mileruiz@hotmail.com ("sandra ruiz"): > I need to know if there is anything like hints of Oracle in > Postgres..otherwise..I wish to find a way to force a query plan to use > the indexes or tell the optimizer things like "optimize based in > statistics", "I want to define the order of the a join" , "optimize > based on a execution plan that I consider the best" ... It is commonly considered a MISFEATURE of Oracle that it forces you to tweak all of those sorts of 'knobs.' The approach taken with PostgreSQL is to use problems discovered to try to improve the quality of the query optimizer. It is usually clever enough to do a good job, and if it can be improved to automatically notice that "better" plan, then that is a better thing than imposing the burden of tuning each query on you. Tom Lane is "Doctor Optimization," and if you look at past discussion threads of this sort, you'll see that he tends to rather strongly oppose the introduction of "hints." -- select 'aa454' || '@' || 'freenet.carleton.ca'; http://www3.sympatico.ca/cbbrowne/linux.html As of next Monday, COMSAT will be flushed in favor of a string and two tin cans. Please update your software.