From: | Stefan Keller <sfkeller(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 9.3 Pre-proposal: Range Merge Join |
Date: | 2013-01-17 20:03:28 |
Message-ID: | CAFcOn2-iy_ZbdOGdwwysATdGiZG144V4VnM=0HrtKNm9bRjb_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Jeff
2012/4/19 Jeff Davis <pgsql(at)j-davis(dot)com>:
> On Wed, 2012-04-18 at 01:21 -0400, Tom Lane wrote:
(...)
>> This is just handwaving of course. I think some digging in the
>> spatial-join literature would likely find ideas better than any of
>> these.
>
> I will look in some more detail. The merge-like approach did seem to be
> represented in the paper referenced by Alexander (the external plane
> sweep), but it also refers to several methods based on partitioning.
>
> I'm beginning to think that more than one of these ideas has merit.
>
> Regards,
> Jeff Davis
I'm perhaps really late in this discussion but I just was made aware
of that via the tweet from Josh Berkus about "PostgreSQL 9.3: Current
Feature Status"
What is the reason to digg into spatial-joins when there is PostGIS
being a bullet-proof and fast implementation?
Yours, Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-01-17 20:24:38 | Re: Event Triggers: adding information |
Previous Message | Josh Berkus | 2013-01-17 20:02:06 | Re: [PATCH]Tablesample Submission |