Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B94779FB303; Fri, 13 Oct 2006 13:36:18 -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 11164-08; Fri, 13 Oct 2006 13:36:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 26A3F9FB3BB; Fri, 13 Oct 2006 13:36:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9DGa4EP025353; Fri, 13 Oct 2006 12:36:04 -0400 (EDT) To: "Jim C. Nasby" cc: Josh Berkus , pgsql-hackers@postgresql.org, pgsql-performance@postgresql.org Subject: Re: [HACKERS] Hints proposal In-reply-to: <20061013161614.GT28647@nasby.net> References: <20061012151439.GT28647@nasby.net> <452E6FFE.7010504@agliodbs.com> <20061012192410.GU28647@nasby.net> <200610121358.22739.josh@agliodbs.com> <20061013161614.GT28647@nasby.net> Comments: In-reply-to "Jim C. Nasby" message dated "Fri, 13 Oct 2006 11:16:14 -0500" Date: Fri, 13 Oct 2006 12:36:04 -0400 Message-ID: <25352.1160757364@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.089 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/271 X-Sequence-Number: 21400 "Jim C. Nasby" writes: > I completely agree that it's much better *in the long run* to improve > the planner and the statistics system so that we don't need hints. But > there's been no plan put forward for how to do that, which means we also > have no idea when some of these problems will be resolved. You keep arguing on the assumption that the planner is static and there's no one working on it. That is false --- although this thread is certainly wasting a lot of time that could have been used more productively ;-). I also dispute your assumption that hints of the style you propose will be easier to implement or maintain than the sort of statistical-assumption tweaking that's been counter-proposed. Just for starters, how are you going to get those hints through the parser and rewriter? That's going to take an entire boatload of very ugly code that isn't needed at all in a saner design. regards, tom lane