Skip to content

Sub-Select in where statement return no data since upgrade to Postgres 10 #172

@ziermach

Description

@ziermach

Hello,

I had same Problem as it is described in #147 .

I could fix this by self compile mysql_fdw with patch from Pull Request #161 .

But now i have another Problem maybe this is in relation to the #147 bug.
I don't get any Data by using sub-selects in where statement this can be simply reproduce.
An short example
location_entity.location is an mysql fdw.

SELECT * FROM location_entity.location WHERE location_id = 5;

works perfectly, but!

SELECT * FROM location_entity.location WHERE location_id = (SELECT 5);

Does not return any result.

I run an Analyse and get this.

Foreign Scan on location (cost=25.01..1025.01 rows=1000 width=534) (actual time=0.320..0.320 rows=0 loops=1) InitPlan 1 (returns $0) -> Result (cost=0.00..0.01 rows=1 width=4) (never executed) Planning time: 1.581 ms Execution time: 3.423 ms (5 rows)

I hope this can be fixed.

Greetings
Christian

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions