[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
pgsql-performance by date
|Next:||From: Dave Dutcher||Date: 2006-09-27 15:51:26|
|Subject: Re: Forcing the use of particular execution plans|
|Previous:||From: Scott Marlowe||Date: 2006-09-27 15:30:59|
|Subject: Re: Merge Join vs Nested Loop|