Re: Merge Join vs Nested Loop - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Merge Join vs Nested Loop
Date
Msg-id 1159370365.4643.7.camel@localhost.localdomain
Whole thread Raw
In response to Re: Merge Join vs Nested Loop  (Tobias Brox <tobias@nordicbet.com>)
Responses Re: Merge Join vs Nested Loop  (Tobias Brox <tobias@nordicbet.com>)
List pgsql-performance
On Wed, 2006-09-27 at 17:05 +0200, Tobias Brox wrote:
> [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.

So, by decreasing them, you should move away from nested loops then,
right?  Has that not worked for some reason?

pgsql-performance by date:

Previous
From: Tobias Brox
Date:
Subject: Re: Merge Join vs Nested Loop
Next
From: Tobias Brox
Date:
Subject: Re: Merge Join vs Nested Loop