Re: BUG #14709: inconsistent answers with foreign data wrappers to mysql

From: Ahsan Hadi <ahsan(dot)hadi(at)enterprisedb(dot)com>
To: Mark Manley <mark(dot)manley(at)tapad(dot)com>
Cc: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, Ibrar Ahmed <ibrar(dot)ahmed(at)enterprisedb(dot)com>
Subject: Re: BUG #14709: inconsistent answers with foreign data wrappers to mysql
Date: 2017-06-21 05:50:33
Message-ID: CAGX_dr1hY7-=ZzD9=v3bMjkjdT=R4wUT4y0wA4NEFjj8UGPCPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The fix for this issue is committed in mysql_fdw github repository, please
see the following mysql_fdw github entry for details...

https://github.com/EnterpriseDB/mysql_fdw/issues/73

Thanks Mark for providing the test case.

On Mon, Jun 19, 2017 at 4:01 PM, Ahsan Hadi <ahsan(dot)hadi(at)enterprisedb(dot)com>
wrote:

> It will be helpful if you can share a test case that can be used to verify
> our fix?
>
> -- Ahsan
>
>
> On Mon, Jun 19, 2017 at 3:57 PM, Mark Manley <mark(dot)manley(at)tapad(dot)com>
> wrote:
>
>> Thank you all. :)
>>
>>
>> On Mon, Jun 19, 2017 at 3:57 AM, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com
>> > wrote:
>>
>>> Hi,
>>>
>>> I informed the maintainer of mysql_fdw and they will start looking into
>>> this issue.
>>>
>>> Thanks,
>>>
>>>
>>> On Mon, Jun 19, 2017 at 4:13 AM, Andrew Gierth <
>>> andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>
>>>> >>>>> "mark" == mark manley <mark(dot)manley(at)tapad(dot)com> writes:
>>>>
>>>> mark> When using a foreign data wrapper from our 9.6.2 database to a
>>>> mark> MySQL 5.7 database, we get inconsistent results. We're joining
>>>> mark> two tables from another server:
>>>>
>>>> mysql_fdw is (and has _always_ been) broken for anything beyond the most
>>>> trivial queries:
>>>>
>>>> https://github.com/EnterpriseDB/mysql_fdw/blob/master/mysql_fdw.c#L734
>>>>
>>>> https://github.com/EnterpriseDB/mysql_fdw/issues/73
>>>>
>>>> Since mysql_fdw is not part of postgresql you should take this up with
>>>> the maintainers. However, the linked issue has been outstanding for 18
>>>> months, so probably best not hold your breath.
>>>>
>>>> --
>>>> Andrew (irc:RhodiumToad)
>>>>
>>>>
>>>> --
>>>> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
>>>> To make changes to your subscription:
>>>> http://www.postgresql.org/mailpref/pgsql-bugs
>>>>
>>>
>>>
>>>
>>> --
>>> Rushabh Lathia
>>> www.EnterpriseDB.com
>>>
>>
>>
>
>
> --
> Ahsan Hadi
> Snr Director Product Development
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>
> Phone: +92-51-8358874 <(051)%208358874>
> Mobile: +92-333-5162114 <0333%205162114>
>
> Website: www.enterprisedb.com
> EnterpriseDB Blog: http://blogs.enterprisedb.com/
> Follow us on Twitter: http://www.twitter.com/enterprisedb
>
> This e-mail message (and any attachment) is intended for the use of the
> individual or entity to whom it is addressed. This message contains
> information from EnterpriseDB Corporation that may be privileged,
> confidential, or exempt from disclosure under applicable law. If you are
> not the intended recipient or authorized to receive this for the intended
> recipient, any use, dissemination, distribution, retention, archiving, or
> copying of this communication is strictly prohibited. If you have received
> this e-mail in error, please notify the sender immediately by reply e-mail
> and delete this message.
>

--
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kaijiang Chen 2017-06-21 08:06:45 Urgent - SQL left join bug?
Previous Message Amit Langote 2017-06-21 02:12:51 Re: Beta 10 parser error for CREATE STATISTICS IF NOT EXISTS