[
https://issues.jboss.org/browse/TEIID-5533?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5533.
-----------------------------------
Fix Version/s: 11.1.2
11.2.1
Resolution: Done
Initially looked to address this with a localized common table in the pg_index definition
- thus the related issues that were logged/addressed TEIID-5531 and TEIID-5532.
TEIID-5529 was a good issue to address in general that was preventing the pushdown of the
oid expression to the subquery evaluation.
Ultimately it's more straight-forward to address by materializing pg_attribute and add
an appropriate index.
With these changes there doesn't seem to be a need for the index materialization to be
a managed load, but that could be added as well.
Improve odbc index metadata query performance
---------------------------------------------
Key: TEIID-5533
URL:
https://issues.jboss.org/browse/TEIID-5533
Project: Teiid
Issue Type: Quality Risk
Components: ODBC
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 11.1.2, 12.0, 11.2.1
For a large number of tables/columns the query for pg_index takes an inordinate amount of
time to complete - for releases after 10.1.1 this will happen only for the initial load.
The structure of the query should be improved as well as a managed materialization load
to better ensure that it does not block a user query.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)