Re: FULL JOIN is only supported with merge-joinable join conditions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "hx(dot)li" <fly2nn(at)126(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: FULL JOIN is only supported with merge-joinable join conditions
Date: 2010-01-06 15:02:06
Message-ID: 1954.1262790126@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"hx.li" <fly2nn(at)126(dot)com> writes:
> ERROR: FULL JOIN is only supported with merge-joinable join conditions
> My question is: why on clause restrict "t_1.a=1"?

It's an implementation restriction. If the clauses aren't mergejoinable
there's no very practical way to keep track of which inner-side rows
have had a match.

> I test it in Oracle, it support to such as "t_1.a=1":

I'd be interested to know how whatever they're doing scales to very
large joins.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dean Rasheed 2010-01-06 15:05:30 Re: set-level update fails with unique constraint violation
Previous Message John T. Dow 2010-01-06 14:53:28 Optimistic locking with multiple rows