Re: Merge join for GiST

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrey Borodin <amborodin(at)acm(dot)org>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergey Mirvoda <sergey(at)mirvoda(dot)com>, Moser Peter <peter(dot)moser(at)unibz(dot)it>
Subject: Re: Merge join for GiST
Date: 2017-04-10 15:38:05
Message-ID: CA+TgmoY8ZyfPBK6KYG3wWNe-H1fOCPp8JPiuv=4hr_n5Bt7a7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 10, 2017 at 7:53 AM, Andrew Borodin <borodin(at)octonica(dot)com> wrote:
> I think this idea is somewhat related to this patch [2], but as for
> now cannot describe how exactly GiST merge and Range Merge features
> relate.

It also seems somewhat related to Peter Moser's work on ALIGN and
NORMALIZE. It would be nice if the various groups of people
interested in improving PostgreSQL's spatial stuff got together and
reviewed each others' patches. As a non-spatial guy myself, it's
pretty hard to decide on the relative merits of different proposed
approaches.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex K 2017-04-10 15:39:16 Re: GSOC'17 project introduction: Parallel COPY execution with errors handling
Previous Message Aleksander Alekseev 2017-04-10 15:35:24 Re: GCC 7 warnings