Re: Rangejoin rebased

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rangejoin rebased
Date: 2018-01-23 05:08:06
Message-ID: CAMp0ubfDLLtnbaHUFEThK5gOx01j4gEAL65UD565oBYx1KszWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 19, 2018 at 2:07 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> err... that isn't correct. An empty range matches nothing, so can be
> ignored in joins.
>
> So probably best to explain some more, please.

The semantics of R1 @> R2 will return true if R1 is a non-NULL range
and R2 is empty.

It's set semantics, and all sets contain the empty set.

But I understand @> is an important case so I am looking into it.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2018-01-23 05:35:14 Query related to alter table ... attach partition
Previous Message Michael Paquier 2018-01-23 04:52:04 Re: [HACKERS] Refactoring identifier checks to consistently use strcmp