Vaibhav Dalvi

@ArazureX , good to know that you are able resolve connection problem. This error is because the data type of _id field is not an ObjectId. Currently, column type NAME...

@ArazureX , this issue is may be due to column data type incompatibility between BOSN type on MongoDB and foreign table column data type on Postgresql. Could you please share...

Thanks for the information. To further investigate this issue, could you please share the data type of remote collection fields and data type of foreign table columns of which value...

Thanks for patches @andreasscherbaum. We have added this in the TODO list, and we will surely look into this.

@andreasscherbaum, as we mentioned we have taken a note of it and added in TODO, and it might NOT be taken immediately, as currently we are working and busy with...

Hi @luhuibiao , Could you please re-check this issue? If it still persists then can you please provide us more details on reproducible test case?

Thanks, @ugurlu for reporting an issue. Could you please provide us the problematic query along with table definitions to look into it further?

Thank you, @ugurlu for detailed information. I can confirm this as a bug with join pushdown. I could reproduce this issue on mongo_fdw latest version i.e. 5.5.1. I have reported...

Hi @lifubang, > select * from tbm_prgs_fdw_temp where code = 'A' and ymd = '20150101'; Currently, this condition in WHERE clause is not going to pushdown because boolean expression or...

@esatterwhite, support of pushing down boolean expression or nested operator expression in WHERE has been already added in the latest version of mongo_fdw i.e. 5.5.0. Please use the latest version...