> and get teiid to use its metadata first?
The current logic is based upon us being a full virtualization layer, so the metadata we present through our pg system tables matches our expectations and is specifically designed for consumption by known odbc clients.
If there is a need, you can certainly have us add more postgresql system tables, but to have them implemented with some interaction with an actual postgresl source is not something that we'd generally want.
makes sense from strategic point of view but it will take a while when Teiid adds full support for native PG clients. Right now, I can't even browse VDB in PG 9.3 admin app due to missing objects in metadata mostly. While our product supports OLE DB for ODBC, the next release of doesn't have OLE DB it which leaves us with only native option. BTW, are there any plans to have increased level of PG compliance in Teiid in the future?
> but it will take a while when Teiid adds full support for native PG clients
As there is virtually no limit to what clients could be doing, we have to add compatibility in a targeted manner.
> are there any plans to have increased level of PG compliance in Teiid in the future
Yes, we are always increasing both the syntax and metadata support. So if there are additional needs that you have, please open a JIRA with the client and/or source queries that it is issuing and we can see about adding more compatibility.