[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5740: --------------------------------------- It looks like the best option is to emulate pg - at least in terms of the sql EXPLAIN ANALYZE with some of the options supported. We of course will return a different plan document, but in some very basic scenarios there will be support. I was also considering if adding some kind of plan information through odata makes any scene, but I don't see that it does at this point. There's no high level concept of an odata plan. For the majority of simple reads there is a direct correspondence of odata query to a sql query, but in many instances multiple queries get issued and we have no good way of tying that information together. On the vdb information we can continue to expand the VIRTUALDATABASE system table for well known properties, but will need to introduce a vdbproperties table or assign some identifier to the vdb itself and reuse the properties table. We'll also want to mimic information_schema representations of grant/role information, but that may need to be spawned as a separate issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)