Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5CF369FB253 for ; Tue, 10 Oct 2006 00:22:31 -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 22535-02 for ; Tue, 10 Oct 2006 00:22:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 7D90C9FB228 for ; Tue, 10 Oct 2006 00:22:27 -0300 (ADT) Received: from [192.168.1.95] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k9A3MOCt015666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Oct 2006 20:22:25 -0700 Message-ID: <452B11FF.5020904@commandprompt.com> Date: Mon, 09 Oct 2006 20:22:39 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.7 (X11/20060918) MIME-Version: 1.0 To: "Craig A. James" CC: Brian Herlihy , Postgresql Performance Subject: Re: Simple join optimized badly? References: <20061010011042.93217.qmail@web52308.mail.yahoo.com> <452B108C.7020703@modgraph-usa.com> In-Reply-To: <452B108C.7020703@modgraph-usa.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 09 Oct 2006 20:22:26 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.189 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/178 X-Sequence-Number: 21307 > Imagine I got run over by a train, and someone was reading my code. > Which would be easier for them to maintain: Code with weird SQL, or code > with sensible, well-written SQL and explicit hints? You forgot the most important option: Code with appropriate documentation about your weird SQL. If you document your code, your argument is moot. Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/