From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: mysql_fdw trouble |
Date: | 2015-10-29 19:01:38 |
Message-ID: | 56326D12.707@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/29/2015 11:20 AM, Dane Foster wrote:
> I think you are correct about mysql_fdw "... sending the trim()
> checks for remote execution" because according to the docs:
>
> "The latest version will push-down the foreign table where clause to
> the foreign server. The where condition on the foreign table will be
> executed on the foreign server hence there will be fewer rows to to
> bring across to PostgreSQL. This is a performance feature."
>
the alternative would be to fetch the whole table across the FDW
interface, then run the where locally, for a large table where you're
only selecting a few rows, this would be very painful.
> I guess using mysql_fdw is a no-go for my data migration needs.
or, rewrite that WHERE clause to be mysql compatible.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2015-10-29 19:05:35 | Re: Configure Different Databases on One Server |
Previous Message | Jim Longwill | 2015-10-29 18:52:34 | Configure Different Databases on One Server |