Closed smilingthax closed 3 months ago
Hi @smilingthax,
Thanks for reporting this issue. I can reproduce the same at my end. We will take this further and try to fix it.
Hi @smilingthax,
We have fixed this issue under commit - https://github.com/EnterpriseDB/mysql_fdw/commit/3548b3354a462da0fab32651dd2a8ce45971726b. Please verify the same at your end and share your feedback. Thanks again for reporting this issue.
I can confirm that my original query (not just the simplified version I gave here) no longer crashes with current git HEAD.
(I did not yet thoroughly check that in all cases the correct result is obtained, though.)
Thanks for the confirmation. We will close this case. If you face any issues further then you can reopen or create new issue anytime.
Preliminaries:
test1 (id int primary key auto_increment, name text not null)
(name
is probably not needed)(Yes, the
r2 IS NULL
(shorthand forr2.* IS NULL
) syntax is uncommon, and not even supported by mysql/mariadb directly. This means it can't be pushed down to mysql and must be evaluated later... But why does the very same thing work forr2
, but not forr3
? Also, the much more commonr3.id IS NULL
does not crash.)mysql_fdw version:
This crashes:
This works (although with a more complicated query plan):
This also works (query plan more similar to the crashing version):
Backtrace of the crashing query: