Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B047F9FB399 for ; Thu, 12 Oct 2006 19:26:45 -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 21576-06 for ; Thu, 12 Oct 2006 19:26:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from linda-3.paradise.net.nz (linda-3.paradise.net.nz [203.96.152.182]) by postgresql.org (Postfix) with ESMTP id 645C09FB35C for ; Thu, 12 Oct 2006 19:26:38 -0300 (ADT) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0J7100AV3NOBDR@linda-3.paradise.net.nz> for pgsql-performance@postgresql.org; Fri, 13 Oct 2006 11:26:36 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-242.dsl.clear.net.nz [218.101.28.242]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 479F1E828BD; Fri, 13 Oct 2006 11:26:35 +1300 (NZDT) Date: Fri, 13 Oct 2006 11:26:34 +1300 From: Mark Kirkwood Subject: Re: FW: Simple join optimized badly? In-reply-to: <20061012163747.GG28647@nasby.net> To: "Jim C. Nasby" Cc: Tom Lane , "H.J. Sanders" , pgsql-performance@postgresql.org Message-id: <452EC11A.2030703@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5.0.7 (X11/20061003) References: <452E11FB.7070704@paradise.net.nz> <20061012135248.GS28647@nasby.net> <10362.1160664260@sss.pgh.pa.us> <20061012163747.GG28647@nasby.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.034 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200610/267 X-Sequence-Number: 21396 Jim C. Nasby wrote: > > Ok, now that I've actually looked at the release notes, I take that back > and apologize. But while there's a lot of improvements that have been > made, there's still some seriously tough problems that have been talked > about for a long time and there's still no "light at the end of the > tunnel", like how to handle multi-column statistics. Yeah - multi-column stats and cost/stats for functions look the the next feature additions we need to get going on.... Cheers Mark