| From: | Andrew Borodin <borodin(at)octonica(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, 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 07:01:46 |
| Message-ID: | CAJEAwVH+YBgfkAtn1qZJhjvbtRPbgzcU3rUt=nJg35hTrsvrYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-04-13 11:30 GMT+05:00 Jeff Davis <pgsql(at)j-davis(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-04-13 07:47:55 | Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. |
| Previous Message | Tsunakawa, Takayuki | 2017-04-13 06:59:59 | Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. |