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

From Tobias Brox
Subject Re: Merge Join vs Nested Loop
Date
Msg-id 20060927152655.GF17834@oppetid.no
Whole thread Raw
In response to Re: Merge Join vs Nested Loop  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: Merge Join vs Nested Loop  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-performance
[Scott Marlowe - Wed at 10:19:24AM -0500]
> So, by decreasing them, you should move away from nested loops then,
> right?  Has that not worked for some reason?

I want to move to nested loops, they are empirically faster in many of
our queries, and that makes sense since we've got quite big tables and
most of the queries only touch a small partition of the data.

I've identified that moving any of the cost constants (including
random_page_cost) upwards gives me the right result, but I'm still wary
if this is the right thing to do.  Even if so, what constants should I
target first?  I could of course try to analyze a bit what constants
give the biggest impact.  Then again, we have many more queries hitting
the database than the few I'm doing research into (and those I'm doing
research into is even very simplified versions of the real queries).

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Merge Join vs Nested Loop
Next
From: Scott Marlowe
Date:
Subject: Re: Merge Join vs Nested Loop