Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 7E4DC1336FA7 for ; Fri, 4 Feb 2011 19:44:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 53446-05 for ; Fri, 4 Feb 2011 23:44:24 +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 E41B31336B42 for ; Fri, 4 Feb 2011 19:44:22 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id 8A8DE3210E for ; Sat, 5 Feb 2011 12:44:21 +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 TTknHfULqA0C for ; Sat, 5 Feb 2011 12:44:20 +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 A67EF32036 for ; Sat, 5 Feb 2011 12:44:20 +1300 (NZDT) Message-ID: <4D4C8F53.8090804@catalyst.net.nz> Date: Sat, 05 Feb 2011 12:44:19 +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: 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> In-Reply-To: <4D4C0EDA.8000704@vmsinfo.com> Content-Type: text/plain; charset=KOI8-U; 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/227 X-Sequence-Number: 42365 On 05/02/11 03:36, Mladen Gogala wrote: > Shaun, I don't need to convince you or the Postgres community. I > needed an argument to convince my boss. > My argument was that the sanctimonious and narrow minded Postgres > community is unwilling to even consider creating the tools I need for > large porting projects, tools provided by other major databases. This > discussion served my purpose wonderfully. Project is killed, here we > part ways. No more problems for either of us. Good luck with the > "perfect optimizer" and good riddance. My only regret is about the > time I have wasted. > I think it is unlikely that your boss is going to dismiss Postgres on the basis of some minor technical point (no optimizer hints). Bosses usually (and should) care about stuff like reference sites, product pedigree and product usage in similar sized companies to theirs. Postgres will come out rather well if such an assessment is actually performed I would think. The real question you should be asking is this: Given that there are no hints, what do I do to solve the problem of a slow query suddenly popping up in production? If and when this situation occurs, see how quickly the community steps in to help you solve it (and it'd bet it will solved be very quickly indeed). Best wishes Mark