Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push JOINs to the fdw level #270

Closed
seacom opened this issue Oct 1, 2021 · 2 comments
Closed

Push JOINs to the fdw level #270

seacom opened this issue Oct 1, 2021 · 2 comments

Comments

@seacom
Copy link

seacom commented Oct 1, 2021

Hi,

from some test with multicorn 1.4.0 and postgresql 13 I'm seeing that JOIN queries are not push down to the foreign sqlalchemy database, instead a SELECT query for every joined table is pushed down and the joining is computed in postgresql.

Is that correct? Is pushing down the JOIN queries something that will be implemented in multicorn in the future?

I think that pushing down that kind of query can reduce both the postgresql load and the network usage between multicorn and the foreign datasource.

@luss
Copy link

luss commented Apr 4, 2022

Please ask this question on https://github.com/pgsql-io/multicorn. In my experience, when pushing down queries in an FDW, you need to convert the pushdown parms to the syntax of the underlying data engine. Offhand, I'm not sure how this could be generalized for Multicorn.

@seacom
Copy link
Author

seacom commented Apr 12, 2022

Thank you for your informations!

@seacom seacom closed this as completed Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants