Re: Status of FDW pushdowns - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Status of FDW pushdowns
Date
Msg-id CAHyXU0z0QFgCM1rxm4URQ10bb1BoPbUs5UxPhxHqhJPazXE2tg@mail.gmail.com
Whole thread Raw
In response to Re: Status of FDW pushdowns  (Shigeru Hanada <shigeru.hanada@gmail.com>)
Responses Re: Status of FDW pushdowns  (David Fetter <david@fetter.org>)
Re: Status of FDW pushdowns  (Shigeru Hanada <shigeru.hanada@gmail.com>)
List pgsql-hackers
On Thu, Nov 21, 2013 at 6:43 PM, Shigeru Hanada
<shigeru.hanada@gmail.com> wrote:
> 2013/11/22 Tom Lane <tgl@sss.pgh.pa.us>:
>> Merlin Moncure <mmoncure@gmail.com> writes:
>>> On Thu, Nov 21, 2013 at 9:05 AM, Bruce Momjian <bruce@momjian.us> wrote:
>>>> I know join pushdowns seem insignificant, but it helps to restrict what
>>>> data must be passed back because you would only pass back joined rows.
>>
>>> By 'insignificant' you mean 'necessary to do any non-trivial real
>>> work'.   Personally, I'd prefer it if FDW was extended to allow
>>> arbitrary parameterized queries like every other database connectivity
>>> API ever made ever.
>>
>> [ shrug... ]  So use dblink.  For better or worse, the FDW stuff is
>> following the SQL standard's SQL/MED design, which does not do it
>> like that.
>
> Pass-through mode mentioned in SQL/MED standard might be what he wants.

happen to have a link handy?

merlin



pgsql-hackers by date:

Previous
From: Jim Mlodgenski
Date:
Subject: Re: Custom Scan APIs (Re: Custom Plan node)
Next
From: Merlin Moncure
Date:
Subject: Re: new unicode table border styles for psql