Skip site navigation (1) Skip section navigation (2)

Re: Merge Join vs Nested Loop

From: Tobias Brox <tobias(at)nordicbet(dot)com>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: Tobias Brox <tobias(at)nordicbet(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Merge Join vs Nested Loop
Date: 2006-09-27 15:36:19
Message-ID: 20060927153619.GG17834@oppetid.no (view raw or flat)
Thread:
Lists: pgsql-performance
[Scott Marlowe - Wed at 10:31:35AM -0500]
> And remember, you can always change any of those settings in session for
> just this one query to force the planner to make the right decision.

sure ... I could identify the most problematic queries, and hack up the
software application to modify the config settings for those exact
queries ... but it's a very ugly solution. :-)  Particularly if Tom Lane
is correct saying the preferance of merge join instead of nested loop is
indeed a bug.

In response to

Responses

pgsql-performance by date

Next:From: Dave DutcherDate: 2006-09-27 15:51:26
Subject: Re: Forcing the use of particular execution plans
Previous:From: Scott MarloweDate: 2006-09-27 15:30:59
Subject: Re: Merge Join vs Nested Loop

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group