2011/1/1 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Dec 30, 2010 at 9:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> On reflection, how about inverting the flag's value and calling it
>>> mergejoin_allowed or some such?
>> Yeah, that's better.
> OK, done that way.
It looks to me like mergejoin_allowed should be initialized to false.
If enable_mergejoin is off and jointype != JOIN_FULL then mergejoin is
not allowed, isn't it? Sorry for noise if it's only my confusing.
In response to
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2011-05-24 14:44:57|
|Subject: Re: pgsql: Support RIGHT and FULL OUTER JOIN in hash joins. |
|Previous:||From: Tom Lane||Date: 2011-05-23 20:35:32|
|Subject: pgsql: Make plpgsql complain about conflicting IN and OUT parameternam|