I was looking at this issue and I wondered why you decided to implement these tables/views under pg_catalog instead of a separate "information_schema" model/schema.

This way the implementation would have been closer to the ANSI-standard and also the potential issue with redirecting queries to an information_schema model added by the user would have been avoided.

Add support for information_schema namespace -------------------------------------------- Key: TEIID-5220 URL: https://issues.jboss.org/browse/TEIID-5220 Project: Teiid Issue Type: Bug Components: ODBC, Query Engine Reporter: Divyesh Vallabh Assignee: Steven Hawkins Priority: Major Fix For: 10.3, 10.2.1 The npgsql provider uses the the infomation_schema namespace to query meta information for tables and views. Add support for information_schema.tables ( https://www.postgresql.org/docs/10/static/infoschema-tables.html) to teiid Add support for information_schema.views ( https://www.postgresql.org/docs/10/static/infoschema-views.html) to teiid Add support for information_schema.columns ( https://www.postgresql.org/docs/10/static/infoschema-columns.html) to teiid