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

From Andrew Borodin
Subject Re: [HACKERS] Merge join for GiST
Date
Msg-id CAJEAwVH+YBgfkAtn1qZJhjvbtRPbgzcU3rUt=nJg35hTrsvrYg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Merge join for GiST  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
2017-04-13 11:30 GMT+05:00 Jeff Davis <pgsql@j-davis.com>:
> I don't quite follow. I don't think any of these proposals uses btree,
> right? Range merge join doesn't need any index, your proposal uses
> gist, and PgSphere's crossmatch uses gist.

Merge join will use presorted data, B-tree provides sorted data.
Merge Join cannot join non-sorted data, can it?

Indeed, B-tree is not the only sorted data provider. In this sight,
Range Merge join is even more generic.

Best regards, Andrey Borodin.



pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby"GUC pseudo-variable.
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.