Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id D2EB7133740B for ; Sat, 5 Feb 2011 01:38:19 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 33371-10 for ; Sat, 5 Feb 2011 05:38:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.catalyst.net.nz (bertrand.catalyst.net.nz [202.78.240.40]) by mail.postgresql.org (Postfix) with ESMTP id A117B1336B42 for ; Sat, 5 Feb 2011 01:38:12 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id 37318320E1; Sat, 5 Feb 2011 18:38:10 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz Received: from mail.catalyst.net.nz ([127.0.0.1]) by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrmZn5XO2NkA; Sat, 5 Feb 2011 18:38:09 +1300 (NZDT) Received: from [192.168.1.11] (122-60-64-230.jetstream.xtra.co.nz [122.60.64.230]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id 65FA131C38; Sat, 5 Feb 2011 18:38:09 +1300 (NZDT) Message-ID: <4D4CE23F.4070500@catalyst.net.nz> Date: Sat, 05 Feb 2011 18:38:07 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Scott Marlowe CC: pgsql-performance@postgresql.org Subject: Re: Talking about optimizer, my long dream References: <4D4C0590.1050609@vmsinfo.com> <4D4C0702.1040909@peak6.com> <4D4C0EDA.8000704@vmsinfo.com> <4D4C8F53.8090804@catalyst.net.nz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201102/236 X-Sequence-Number: 42374 O > If Oracle can patch their query planner for you in 24 hours, and you > can apply patch with confidence against your test then production > servers in an hour or so, great. Til then I'll stick to a database > that has the absolutely, without a doubt, best coder support of any > project I've ever used. > > My point in the other thread is that if you can identify a point where > a hint would help, like my situation above, you're often better off > presenting a test case here and getting a patch to make it smarter. > By way of contrast - I had a similar situation with DB2 (a few years ago) with a bad plan being chosen for BETWEEN predicates in some cases. I found myself having to spend about a hour or two a week chasing the support organization for - wait for it - 6 months to get a planner patch!