X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 67D79D1CB3F for ; Wed, 17 Dec 2003 01:17:54 +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 40437-05 for ; Tue, 16 Dec 2003 21:17:26 -0400 (AST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id B8648D1CB21 for ; Tue, 16 Dec 2003 21:17:22 -0400 (AST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 6C5DF3524B; Tue, 16 Dec 2003 17:17:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 6AEF734DBC; Tue, 16 Dec 2003 17:17:26 -0800 (PST) Date: Tue, 16 Dec 2003 17:17:26 -0800 (PST) From: Stephan Szabo To: Nick Fankhauser Cc: "Pgsql-Performance@Postgresql. Org" Subject: Re: Nested loop performance In-Reply-To: Message-ID: <20031216171625.A31260@megazone.bigpanda.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/247 X-Sequence-Number: 5107 On Tue, 16 Dec 2003, Nick Fankhauser wrote: > Is there a more efficient means than a nested loop to handle such a join? > Would a different method be chosen if there was exactly one row in > actor_summary for every row in actor? As a question, what does explain analyze give you if you set enable_nestloop=false; before trying the query?