| 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-19 10:07:47 |
| Message-ID: | CANP8+j+QRbpFjBLezj_bOEeUU3f=sLegtbxM1DqP0s5W9MO0eQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 January 2018 at 08:25, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 17 January 2018 at 05:49, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>> On Wed, Jan 10, 2018 at 7:49 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> Do we optimize for TIMESTAMP <@ RANGE as well?
>>
>> Not currently. It requires a little extra complexity because empty
>> ranges will match anything and need special handling.
err... that isn't correct. An empty range matches nothing, so can be
ignored in joins.
So probably best to explain some more, please.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-01-19 10:14:14 | Re: [HACKERS] Useless code in ExecInitModifyTable |
| Previous Message | Yoshimi Ichiyanagi | 2018-01-19 09:56:26 | Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory |