| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs |
| Date: | 2015-01-06 07:17:54 |
| Message-ID: | CABOikdMiB+Cu9fic6wNw=LOQEpPMBkF+pNqoAcOKuT1xxjRJkg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 6, 2015 at 12:38 PM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
>
>
> On Tue, Jan 6, 2015 at 12:29 PM, Amit Langote <
> Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
>>
>> >
>>
>> Sounds something like ORDERED BY x implying output is "known" ordered by
>> x perhaps enough hint for the planner to make necessary plan choices
>> though I may be wrong.
>>
>>
>>
> I may be missing something, but isnt what you mentioned the exact
> functionality this patch adds?
>
May be what Amit has in mind is that the planner can choose the most
optimal sorting algorithm using the hint that the dataset is probably
already sorted. Actually why not just do that? Though AFAIK its against
our stated policy of not adding any planner hints.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2015-01-06 07:23:59 | Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs |
| Previous Message | Amit Langote | 2015-01-06 07:13:57 | Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs |