Re: merge join killing performance - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: merge join killing performance
Date
Msg-id AANLkTinBVZmcknJjIQGr_suUnlOoBE8uxG-vGfiA7KWQ@mail.gmail.com
Whole thread Raw
In response to Re: merge join killing performance  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: merge join killing performance  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Thu, May 27, 2010 at 7:16 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Scott Marlowe <scott.marlowe@gmail.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.

Cool, do we have a snapshot build somewhere or do I need to get all
the extra build bits like flex or yacc or bison or whatnot?

pgsql-performance by date:

Previous
From: Mark Wong
Date:
Subject: hp hpsa vs cciss driver
Next
From: Tom Lane
Date:
Subject: Re: merge join killing performance