Re: Range Types

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Range Types
Date: 2011-02-09 08:35:28
Message-ID: 1297240528.27157.463.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Updated patch.

* Addressed Erik's review comments.
* Fixed issue with "range @> elem" found by Erik.
* Merged with latest HEAD
* Changed representation to be more efficient and more robust
(could use some testing though, because I just did this tonight)

* send/recv -- just noticed this tonight, no reason not to do it

Open Items:
* Maybe typmod
* grammar -- ask for btree opclass, or compare function?
* catalog -- store btree opclass, or compare function?
* should non-superusers be able to create range types?
* constructor issues I just posted about
* SQL length function --immutable/stable/volatile?

As always, my repo is here:;a=log;h=refs/heads/rangetypes

Jeff Davis

Attachment Content-Type Size
rangetypes-20110208.patch.gz application/x-gzip 38.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-02-09 08:38:25 Re: [PERFORM] pgbench to the MAXINT
Previous Message Magnus Hagander 2011-02-09 08:12:32 Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,