[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- See the sql above. The settings are per server: CREATE SERVER teiid_server FOREIGN DATA WRAPPER postgres_fdw OPTIONS (host 'TEIID_SERVICE_HOST', port 'TEIID_SERVICE_PORT', dbname 'VDB'); -- note, this performs no initial validation CREATE USER MAPPING FOR pg_user SERVER teiid_server OPTIONS (user 'TEIID_SECRET_USER', password 'TEIID_SECRET_PASSWORD'); The only thing we could do is have a single pg instance have multiple databases - which is not something the default install is setup to do. Without a patch of the pg fdw there's nothing we can do. The logic expects the local schema name to be the same at remote. With pg managed materialization there are no additional choices as of yet. It's only a full refresh - that can be manual, timed, or if we retain a status table based upon some update threshold. What do you mean by implicitly trusted over service? I'm saying that boils down to client ip or certificate (either of which would need additional logic). -- This message was sent by Atlassian Jira (v7.12.1#712002)