| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Getting sorted data from foreign server for merge join |
| Date: | 2015-11-10 00:35:01 |
| Message-ID: | 56413BB5.7020006@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015/11/10 0:56, Robert Haas wrote:
> On Sat, Nov 7, 2015 at 12:07 PM, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
>> Sorry to barge in late, but I was wondering if what we've learned with this
>> patch can be applied to the case of asserting a sort order on a query
>> returning from dblink().
>
> Nope.
>
> Sorry to the bearer of bad news, but that would be a different and
> much harder development project. Set-returning functions have no way
> to indicate anything about the ordering of their return values at
> present. We could invent something, but the work involved wouldn't
> have much to do with this patch.
There was a patch (which, it seems, was rejected [1]) to do this sort of
thing.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-10 00:46:37 | Re: Uh-oh: documentation PDF output no longer builds in HEAD |
| Previous Message | Andres Freund | 2015-11-09 22:10:13 | Re: Move PinBuffer and UnpinBuffer to atomics |