Re: WIP: Range Types

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: Range Types
Date: 2011-01-08 20:47:16
Message-ID: AANLkTimQS1N0YwpXHrMPFsAzCrxeFdyvKaF8+Y=vPc1X@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 8, 2011 at 3:12 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> Any ideas? Maybe, with alignment and a "flags" byte (to hold
> inclusivity, infinite boundaries, etc.), the extra 4 bytes doesn't cost
> much, anyway?

I'd be really reluctant to bloat the range representation by 4 bytes
to support an anyrange type. Better to defer this until the great day
when we get a better typmod system, at least IMHO.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-01-08 21:05:55 Re: WIP: Range Types
Previous Message Robert Haas 2011-01-08 20:44:09 Re: obj_unique_identifier(oid)