Re: Range Types: << >> -|- ops vs empty range - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Range Types: << >> -|- ops vs empty range
Date
Msg-id 201103111337.p2BDb8011923@momjian.us
Whole thread Raw
In response to Re: Range Types: << >> -|- ops vs empty range  ("Erik Rijkers" <er@xs4all.nl>)
Responses Re: Range Types: << >> -|- ops vs empty range
List pgsql-hackers
Where are we on this?

---------------------------------------------------------------------------

Erik Rijkers wrote:
> On Wed, February 9, 2011 09:35, Jeff Davis wrote:
> > Updated patch.
> >
> 
> The operators  <<  >>  and -|-  have the following behavior with empty ranges:
> 
> testdb=# select '-'::int4range << range(200,300);
> ERROR:  empty range
> testdb=# select '-'::int4range >> range(200,300);
> ERROR:  empty range
> testdb=# select '-'::int4range -|- range(200,300);
> ERROR:  empty range
> 
> I'm not sure if that is deliberate behavior, but they seem
> almost bugs to me.
> 
> Wouldn't it be better (and more practical) if these would
> return false (or perhaps NULL, for 'unknown') ?
> 
> (the same goes for all the other range types, btw.)
> 
> 
> Erik Rijkers
> 
> 
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Replication server timeout patch
Next
From: Bruce Momjian
Date:
Subject: Re: pg_terminate_backend and pg_cancel_backend by not administrator user