Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DB3519F9F74 for ; Tue, 17 Oct 2006 23:43:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 32824-04 for ; Tue, 17 Oct 2006 23:43:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from n007.sc1.cp.net (smtpout1485.sc1.he.tucows.com [64.97.157.185]) by postgresql.org (Postfix) with ESMTP id ADC429FA086 for ; Tue, 17 Oct 2006 23:43:09 -0300 (ADT) Received: from [192.168.0.12] (68.34.49.125) by n007.sc1.cp.net (7.2.069.1) (authenticated as rob@treat.com) id 453579ED00004B56; Wed, 18 Oct 2006 02:43:04 +0000 From: Robert Treat To: pgsql-performance@postgresql.org Subject: Re: Hints proposal Date: Tue, 17 Oct 2006 22:40:19 -0400 User-Agent: KMail/1.9.1 Cc: "Bucky Jordan" , "Joshua Marsh" References: <78ED28FACE63744386D68D8A9D1CF5D4209C9A@MAIL.corp.lumeta.com> In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209C9A@MAIL.corp.lumeta.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200610172240.20142.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.55 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/337 X-Sequence-Number: 21466 On Thursday 12 October 2006 12:40, Bucky Jordan wrote: > >What is it about hinting that makes it so easily breakable with new > > versions?=A0 I >don't have any experience with Oracle, so I'm not sure = how > > they screwed logic like >this up.=A0=A0 > > I don't have a ton of experience with oracle either, mostly DB2, MSSQL and > PG. So, I thought I'd do some googling, and maybe others might find this > useful info. > > http://asktom.oracle.com/pls/ask/f?p=3D4950:8:2177642270773127589::NO::F4= 950_ >P8_DISPLAYID,F4950_P8_CRITERIA:7038986332061 > > Interesting quote: "In Oracle Applications development (11i apps - HR, CR= M, > etc) Hints are strictly forbidden. We find the underlying cause and fix > it." and "Hints -- only useful if you are in RBO and you want to make use > of an access path." > > Maybe because I haven't had access to hints before, I've never been tempt= ed > to use them. However, I can't remember having to re-write SQL due to a PG > upgrade either. > When it happens it tends to look something like this: http://archives.postgresql.org/pgsql-performance/2006-01/msg00154.php =46unny that for all the people who claim that improving the planner should= be=20 the primary goal that no one ever took interest in the above case. =20 =2D-=20 Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL