Re: merge join killing performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: merge join killing performance
Date: 2010-05-28 01:16:26
Message-ID: 15062.1275009386@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> So, Tom, so you think it's possible that the planner isn't noticing
> all those nulls and thinks it'll just take a row or two to get to the
> value it needs to join on?

I've committed a patch for this, if you're interested in testing that
it fixes your situation.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message KaiGai Kohei 2010-05-28 01:30:36 Re: [RFC] Security label support
Previous Message Tatsuo Ishii 2010-05-28 01:10:07 Re: pg_trgm

Browse pgsql-performance by date

  From Date Subject
Next Message Mark Wong 2010-05-28 01:24:17 hp hpsa vs cciss driver
Previous Message Krzysztof Nienartowicz 2010-05-27 23:04:17 Re: Query causing explosion of temp space with join involving partitioning