| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rangejoin rebased |
| Date: | 2018-01-10 15:49:18 |
| Message-ID: | CANP8+jK+es0yjfa-AB8R49KFa912rT-O-O_XL=X=xGJYnjEDBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10 January 2018 at 04:24, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Sat, Jan 6, 2018 at 10:38 AM, Simon Riggs <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-01-10 16:08:53 | let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status) |
| Previous Message | Alvaro Herrera | 2018-01-10 15:37:07 | Re: [HACKERS] Proposal: Local indexes for partitioned table |