[teiid-issues] [JBoss JIRA] (TEIID-4122) Improve performance of odbc client column metadata query

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-4122.
-----------------------------------
    Fix Version/s: 9.0
                       (was: 9.1)
       Resolution: Done


With more investigation the changes here are:

add some more compliance around command complete and counts
add a specific query override for the column metadata that avoids several joins and the overhead of the pg_attribute table
allow materialization to take place proactively

> Improve performance of odbc client column metadata query
> --------------------------------------------------------
>
>                 Key: TEIID-4122
>                 URL: https://issues.jboss.org/browse/TEIID-4122
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: ODBC
>            Reporter: Steven Hawkins
>             Fix For: 9.0
>
>
> With cursoring, the client issues:
> select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = <table oid>) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum
> We should ensure that this is being planned optimally.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)