Re: Rangejoin rebased - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Rangejoin rebased
Date
Msg-id CANP8+jK+es0yjfa-AB8R49KFa912rT-O-O_XL=X=xGJYnjEDBQ@mail.gmail.com
Whole thread Raw
In response to Re: Rangejoin rebased  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Rangejoin rebased
List pgsql-hackers
On 10 January 2018 at 04:24, Jeff Davis <pgsql@j-davis.com> wrote:
> On Sat, Jan 6, 2018 at 10:38 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> For this to be useful, it needs to include some details of how to use
>> it when people have NOT used range datatypes in their tables.
>
> Good idea. I added an example that doesn't have range types in the base table.

Cool, thanks

...


It would be useful to consider any related use cases.
Are there applications for range operators other than &&?

Do we optimize for TIMESTAMP <@ RANGE as well?

Does this link in nicely with partition-aware joins?
Does it allow partition exclusion if you join a daterange to a time
range partitioned table?

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Proposal: Local indexes for partitioned table
Next
From: Robert Haas
Date:
Subject: let's make the list of reportable GUCs configurable (was Re: Add %rsubstitution for psql prompts to show recovery status)