X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1F07B9DC840 for ; Tue, 7 Mar 2006 11:36:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47851-04 for ; Tue, 7 Mar 2006 11:36:16 -0400 (AST) 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 E0B7A9DCBD2 for ; Tue, 7 Mar 2006 11:36:09 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k27FYvds018786; Tue, 7 Mar 2006 10:34:58 -0500 (EST) To: "Dave Dutcher" cc: "'Chris'" , "'i.v.r.'" , pgsql-performance@postgresql.org Subject: Re: Help understanding indexes, explain, and optimizing In-reply-to: <003b01c641f8$39185a70$8300a8c0@tridecap.com> References: <003b01c641f8$39185a70$8300a8c0@tridecap.com> Comments: In-reply-to "Dave Dutcher" message dated "Tue, 07 Mar 2006 09:02:58 -0600" Date: Tue, 07 Mar 2006 10:34:57 -0500 Message-ID: <18785.1141745697@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.112 required=5 tests=[AWL=0.112] X-Spam-Score: 0.112 X-Spam-Level: X-Archive-Number: 200603/58 X-Sequence-Number: 17495 "Dave Dutcher" writes: > It sounds like the original posters problem was a less than optimal join > order, and from what I understand Postgres can't reorder left joins. Not really relevant to the OP's immediate problem, but: that's fixed in CVS HEAD. http://archives.postgresql.org/pgsql-hackers/2005-12/msg00760.php http://archives.postgresql.org/pgsql-committers/2005-12/msg00352.php regards, tom lane