Re: mysql_fdw trouble

From: Dane Foster <studdugie(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: mysql_fdw trouble
Date: 2015-10-29 18:20:46
Message-ID: CA+Wxin+gKig3dPF4x9wsxrEbThWaiCOum0s+FMujtkiuRFGSZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 29, 2015 at 2:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Dane Foster <studdugie(at)gmail(dot)com> writes:
> > Installation and set up worked flawlessly but when I run the following
> query
> > ...
> > ​I get the following error:​
> > ​ERROR: failed to prepare the MySQL query:
> > FUNCTION latest.btrim does not exist
>
> It looks like mysql_fdw is messing up by sending the trim() checks for
> remote execution when there is no suitable function on the remote side.
> Don't know whether that's a bug in mysql_fdw, or whether there's some
> setup you're supposed to perform on the mysql server and have omitted.
>
> regards, tom lane
>
​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."
I guess using mysql_fdw is a no-go for my data migration needs.

Dane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-10-29 18:28:01 Re: mysql_fdw trouble
Previous Message Adrian Klaver 2015-10-29 18:13:02 Re: does pg_dump get delayed if I have a loop that does continuous insertions