Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackers
Updated patch.

Changes:
  * 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)

TODO:
  * 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:

http://git.postgresql.org/gitweb?p=users/jdavis/postgres.git;a=log;h=refs/heads/rangetypes

Regards,
	Jeff Davis

Attachment: rangetypes-20110208.patch.gz
Description: application/x-gzip (38.6 KB)

In response to

Responses

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group