Re: Measure Theoretic Data Types in Postgresql

From: Nathan Boley <npboley(at)gmail(dot)com>
To: Aaron Sheldon <aaron(dot)sheldon(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Measure Theoretic Data Types in Postgresql
Date: 2012-10-12 17:41:58
Message-ID: CAHetpQRFHFBA4A2u-iG1FmNtSLcHDWOgSc8Jbs7fFbfcxd4j6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> However, by realizing that the bounds on the ranges have a linear ordering
> one can speed this up to 0(m) using windowing functions on common table
> expressions.
>
> So what I am proposing is formalizing this optimization into a class of data
> types, that will hide the implementation details.

Could this not also be handled by extending merge join to work with an
overlap operator?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2012-10-12 17:50:06 problem with mailing list
Previous Message Bruce Momjian 2012-10-12 17:35:48 Re: getopt() and strdup()