On Thu, May 27, 2010 at 7:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
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?
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2010-05-28 02:56:12|
|Subject: Re: merge join killing performance |
|Previous:||From: Mark Wong||Date: 2010-05-28 01:24:17|
|Subject: hp hpsa vs cciss driver|
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-05-28 02:47:57|
|Subject: Re: tsvector pg_stats seems quite a bit off. |
|Previous:||From: Fujii Masao||Date: 2010-05-28 02:42:50|
|Subject: Re: quoting and recovery.conf|