[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4251 at 10/4/18 11:45 AM: ----------------------------------------------------------------- Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for It appears that the logic requires a local schema that matches the remote. Otherwise the query sent to the remote will be qualified with the wrong (local) schema name. It also fixes the import problem - so import ... "SYS" into sys is fine, but import ... "SYS" into public doesn't work. - the execution against a foreign table uses a prepared cursor syntax than we currently have support for - local names must match exactly, so quoted with case that matches Teiid - IMPORT FOREIGN SCHEMA "SYS" - as generated queries end up using predicates like name = '...' was (Author: shawkins): Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for - the execution against a foreign table uses a prepared cursor syntax than we currently have support for -- This message was sent by Atlassian Jira (v7.12.1#712002)