On 19 January 2018 at 08:25, Simon Riggs <[email protected]> wrote: > On 17 January 2018 at 05:49, Jeff Davis <[email protected]> wrote: >> On Wed, Jan 10, 2018 at 7:49 AM, Simon Riggs <[email protected]> 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
