On Wed, Feb 15, 2017 at 3:33 PM, David G. Johnston <david.g.johns...@gmail.com> wrote: > The description in the OP basically distinguishes between NORMALIZE and > ALIGN in that ALIGN, as described above, affects an INTERSECTION on the two > ranges - discarding the non-overlapping data - while NORMALIZE performs the > alignment while also retaining the non-overlapping data.
Hmm. So is ALIGN like an inner join and NORMALIZE like a full outer join? Couldn't you have left and right outer joins, too, like you null-extend the parts of the lefthand range that don't match but throw away parts of the righthand range that don't match? Also, it sounds like all of this is intended to work with ranges that are stored in different columns rather than with PostgreSQL's built-in range types. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
