Re: [HACKERS] Merge join for GiST - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: [HACKERS] Merge join for GiST
Date
Msg-id CAMp0ubfOZ7u2h_zC7WhUKW19+CzpqT2RcQ6nTzfXiD00UWc3PA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Merge join for GiST  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: [HACKERS] Merge join for GiST  (Andrew Borodin <borodin@octonica.com>)
List pgsql-hackers
On Tue, Apr 11, 2017 at 8:35 AM, Alexander Korotkov
<a.korotkov@postgrespro.ru> wrote:
> On Tue, Apr 11, 2017 at 5:46 PM, Jeff Davis <pgsql@j-davis.com> wrote:
>> Do you have a sense of how this might compare with range merge join?
>
>
> If you have GiST indexes over ranges for both sides of join, then this
> method could be used for range join.  Hence, it could be compared with range
> merge join.
> However, particular implementation in pgsphere uses hardcoded datatypes and
> operations.
> Thus, for range join we need either generalized version of GiST-based join
> or special implementation for ranges.

Alexander, Andrew,

How do you think we should proceed? Which projects do you think should
eventually be in core, versus which are fine as extensions?

Regards,    Jeff Davis



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] pg_dump emits ALTER TABLE ONLY partitioned_table
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Tab completion support for ALTER SUBSCRIPTION REFRESH PUBLICATION