Re: ERROR: FULL JOIN is only supported with merge-joinable join conditions - Mailing list pgsql-general

From Tom Lane
Subject Re: ERROR: FULL JOIN is only supported with merge-joinable join conditions
Date
Msg-id 7935.1142266716@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: FULL JOIN is only supported with merge-joinable join conditions  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: ERROR: FULL JOIN is only supported with merge-joinable  (Harco de Hilster <Harco.de.Hilster@ATConsultancy.nl>)
List pgsql-general
Martijn van Oosterhout <kleptog@svana.org> writes:
> I think the reason it hasn't been done for general join conditions is
> because we havn't thought of an efficient algorithm.

Right, it's keeping track of the unmatched right-hand rows that's a
problem.

> However, I wonder if youre case couldn't be handled with a
> time-interval datatype such that you condition is merge-joinable on
> that type. I can't quite see it though...

Interesting thought.  The use of NULLs in this example is a pretty poor
representational choice --- the queries would get a lot simpler if you
used "exptime = INFINITY" to represent unexpired data.  That doesn't get
you all the way to a mergejoinable query though :-(

            regards, tom lane

pgsql-general by date:

Previous
From: Prestation3.EXPLOITATION@nexans.com
Date:
Subject: dump from old version
Next
From: Emi Lu
Date:
Subject: Re: in Pl/PgSQL, do commit every 5000 records