pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

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:36:19 +0200
Message-ID: <20060927153619.GG17834@oppetid.no> (raw)
In-Reply-To: <1159371095.26848.84.camel@state.g2switchworks.com>
References: <20060926193553.GA27268@oppetid.no>
	<719.1159308596@sss.pgh.pa.us>
	<20060927094803.GA11245@oppetid.no>
	<1159369111.4643.0.camel@localhost.localdomain>
	<20060927150512.GE17834@oppetid.no>
	<1159370365.4643.7.camel@localhost.localdomain>
	<20060927152655.GF17834@oppetid.no>
	<1159371095.26848.84.camel@state.g2switchworks.com>

[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.

view thread (10+ messages)  latest in thread

Message-ID: <20060927153619.GG17834@oppetid.no>
Permalink:  ../20060927153619.GG17834@oppetid.no/
Also on:    postgresql.org/message-id/20060927153619.GG17834@oppetid.no

copy link · copy postgr.es

reply

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: <20060927153619.GG17834@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