Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

From: Peter Moser <pitiz29a(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] [PROPOSAL] Temporal query processing with range types
Date: 2018-01-26 06:56:23
Message-ID: CAHO0eLZRLghN=ni08v4j5SdFWr8xWupSOwHbdUYorKnBN==Cjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2018-01-06 at 20:29 +0000, Simon Riggs wrote:
> * various PostJoinSetProjection() functions to be called as needed
> So the idea is we enable Postgres to allow major new functionality,
> as was done for PostGIS so successfully.

If we use a post-join approach many intermediate result tuples, that do
not contribute to the final result would be emmitted, and thus the
performance would suffer.

Best regards,
Anton, Johann, Michael, Peter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Moser 2018-01-26 06:57:25 Re: [HACKERS] [PROPOSAL] Temporal query processing with range types
Previous Message Peter Moser 2018-01-26 06:55:11 Re: [HACKERS] [PROPOSAL] Temporal query processing with range types