X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5DADCD1DA5F for ; Sun, 28 Mar 2004 17:17:37 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 98830-09 for ; Sun, 28 Mar 2004 13:17:36 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 45589D1D8F3 for ; Sun, 28 Mar 2004 13:17:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2SHGI2f016580; Sun, 28 Mar 2004 12:16:19 -0500 (EST) To: "Eric Brown" Cc: pgsql-performance@postgresql.org Subject: Re: severe performance issue with planner In-reply-to: References: Comments: In-reply-to "Eric Brown" message dated "Mon, 22 Mar 2004 20:30:29 -0500" Date: Sun, 28 Mar 2004 12:16:18 -0500 Message-ID: <16579.1080494178@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/400 X-Sequence-Number: 6256 "Eric Brown" writes: > Here's the query as I have changed it now: Now that you've switched to JOIN syntax, you can cut the planning time to nil by setting join_collapse_limit to 1. See http://www.postgresql.org/docs/7.4/static/explicit-joins.html regards, tom lane