| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Range Types: empty ranges |
| Date: | 2011-02-11 20:40:52 |
| Message-ID: | 1297456852.801.16.camel@jdavis-ux.asterdata.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2011-02-11 at 15:14 -0500, Robert Haas wrote:
> On Fri, Feb 11, 2011 at 3:03 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > Well, there is a certain amount of localized clarity, I will agree with
> > that. The complexity comes when you accidentally rely on some
> > transformation which seems logically sound, but could result in a
> > transient empty range, which then throws an error.
>
> But by this argument you also need to support discontiguous ranges, don't you?
>
> I mean, if you want to insist that A intersect B has to still be a
> legal range, what about A union B?
>
I responded to a similar question/point here:
http://archives.postgresql.org/pgsql-hackers/2011-02/msg01073.php
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2011-02-11 20:44:22 | Fix for Index Advisor related hooks |
| Previous Message | Dimitri Fontaine | 2011-02-11 20:40:08 | Re: ALTER EXTENSION UPGRADE, v3 |