Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Support RIGHT and FULL OUTER JOIN in hash joins.

From: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Support RIGHT and FULL OUTER JOIN in hash joins.
Date: 2011-05-24 09:59:22
Message-ID: BANLkTinio_qPOZz7rcz-6f+wB+N5H34eRg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committers
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.

Regards,

-- 
Hitoshi Harada

In response to

Responses

pgsql-committers by date

Next:From: Tom LaneDate: 2011-05-24 14:44:57
Subject: Re: pgsql: Support RIGHT and FULL OUTER JOIN in hash joins.
Previous:From: Tom LaneDate: 2011-05-23 20:35:32
Subject: pgsql: Make plpgsql complain about conflicting IN and OUT parameternam

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group