You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: