From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Nick Fankhauser <nickf@ontko.com>
Cc: Pgsql-Performance@Postgresql. Org <pgsql-performance@postgresql.org>
Subject: Re: Nested loop performance
Date: Tue, 16 Dec 2003 17:17:26 -0800 (PST)
Message-ID: <20031216171625.A31260@megazone.bigpanda.com> (raw)
In-Reply-To: <NEBBLAAHGLEEPCGOBHDGOEJMKBAA.nickf@ontko.com>
References: <NEBBLAAHGLEEPCGOBHDGOEJMKBAA.nickf@ontko.com>
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sszabo@megazone.bigpanda.com, nickf@ontko.com
Subject: Re: Nested loop performance
In-Reply-To: <20031216171625.A31260@megazone.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox