| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rangejoin rebased |
| Date: | 2018-01-15 15:36:21 |
| Message-ID: | CA+Tgmoa9PpvRXzXOVgzHArC8MJUqzzyAXBML3i-aCw5MOd7J9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 9, 2018 at 11:24 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>> Just to emphasise why we want this, it might be better for the EXPLAIN
>> to say "Time Range Join" when the ranges being joined are Time Ranges,
>> and for other cases to just say "Range Join". The use of the word
>> Merge doesn't help much there.
>
> I don't care for special-casing the word "time" in there, because no
> other type would benefit. It seems a little too magical. I also do
> like leaving "merge" in there because it helps the user understand why
> their inputs are being sorted.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-01-15 15:48:55 | Re: proposal: alternative psql commands quit and exit |
| Previous Message | Robert Haas | 2018-01-15 15:32:56 | Re: proposal: alternative psql commands quit and exit |