Re: [GENERAL] btree gist indices, null and open-ended tsranges

On 12/11/2016 11:34 PM, Chris Withers wrote: > On 01/12/2016 12:12, Francisco Olarte wrote: >> On Thu, Dec 1, 2016 at 12:56 PM, Chris Withers >> wrote: >>> So, first observation: if I make room nullable, the exclude >>> constraint does >>> not apply for rows that have a

Re: [GENERAL] btree gist indices, null and open-ended tsranges

On 01/12/2016 12:12, Francisco Olarte wrote: On Thu, Dec 1, 2016 at 12:56 PM, Chris Withers wrote: So, first observation: if I make room nullable, the exclude constraint does not apply for rows that have a room of null. I guess that's to be expected, right? I would

Re: [GENERAL] btree gist indices, null and open-ended tsranges

Hi Chris: On Thu, Dec 1, 2016 at 12:56 PM, Chris Withers wrote: > So, first observation: if I make room nullable, the exclude constraint does > not apply for rows that have a room of null. I guess that's to be expected, > right? I would expect it, given: n=> select

[GENERAL] btree gist indices, null and open-ended tsranges

Hi All, Working with the exclude constraint example from https://www.postgresql.org/docs/current/static/rangetypes.html: CREATE EXTENSION btree_gist; CREATE TABLE room_reservation ( room text, during tsrange, EXCLUDE USING GIST (room WITH =, during WITH &&) ); So, first