| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Andrew Borodin <amborodin(at)acm(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergey Mirvoda <sergey(at)mirvoda(dot)com> |
| Subject: | Re: Merge join for GiST |
| Date: | 2017-04-13 02:01:52 |
| Message-ID: | CAMp0ubfOZ7u2h_zC7WhUKW19+CzpqT2RcQ6nTzfXiD00UWc3PA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 11, 2017 at 8:35 AM, Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> On Tue, Apr 11, 2017 at 5:46 PM, Jeff Davis <pgsql(at)j-davis(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-04-13 02:05:09 | Re: Tab completion support for ALTER SUBSCRIPTION REFRESH PUBLICATION |
| Previous Message | Amit Langote | 2017-04-13 01:57:26 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |