From: Tobias Brox <tobias@nordicbet.com>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Merge Join vs Nested Loop
Date: Wed, 27 Sep 2006 17:05:12 +0200
Message-ID: <20060927150512.GE17834@oppetid.no> (raw)
In-Reply-To: <1159369111.4643.0.camel@localhost.localdomain>
References: <20060926193553.GA27268@oppetid.no>
<719.1159308596@sss.pgh.pa.us>
<20060927094803.GA11245@oppetid.no>
<1159369111.4643.0.camel@localhost.localdomain>
[Scott Marlowe - Wed at 09:58:30AM -0500]
> Have you tried chaning the cpu_* cost options to see how they affect
> merge versus nested loop?
As said in the original post, increasing any of them shifts the planner
towards nested loops instead of merge_join. I didn't check which one of
the cost constants made the most impact.
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: tobias@nordicbet.com, smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us
Subject: Re: Merge Join vs Nested Loop
In-Reply-To: <20060927150512.GE17834@oppetid.no>
* 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