[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5963: --------------------------------------- I can't reproduce this behavior. I'm not sure what the wire level pg message exchange is showing in terms of metadata load. At least with master with the foreign schema name in the import statement it gets passed to the jdbc metadata importer as importer.schemaName=name, which then limits the scope of what is imported. Please try to reproduce this on Teiid 13.1+ Moving forward to 13+ with https://issues.redhat.com/browse/TEIID-5850 A create foreign data wrapper without any options is not necessary, so you would use: CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true); Not CREATE FOREIGN DATA WRAPPER postgresql; Also even in 12.x the only properties used on create server are related to the source, not the translator. With: CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true); The supportsOrderBy is effectively ignored. -- This message was sent by Atlassian Jira (v7.13.8#713008)