| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Foreign data wrappers and indexes on remote side |
| Date: | 2015-06-26 16:21:40 |
| Message-ID: | CAKFQuwZyvjYciSaKS3of3hg4nuPP7mRos4p3f+JOkAXHnsAHiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 26, 2015 at 12:09 PM, Filip Rembiałkowski <
filip(dot)rembialkowski(at)gmail(dot)com> wrote:
> Hi.
>
> Is there any way to take use of indexes on foreign tables?
>
> Currently (at least with tds_fdw, that I was testing) the planner just
> does a dumb full sequential scan in all cases.
>
> That is
>
> SELECT drink FROM foreignbar;
>
> -- takes as much time as
>
> SELECT drink FROM foreignbar where drink_key = 3210;
>
It is possible but implementation is the responsibility of the FDW
middleware authors.
Since "tds_fdw" is not core this would not be the correct forum.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-06-26 16:23:33 | Re: Functions, savepoints, autocommit = I am confused ! |
| Previous Message | Tom Lane | 2015-06-26 16:19:45 | Re: Foreign data wrappers and indexes on remote side |