Feedback
Did this article resolve your question/issue?

   

Article

Bad performance when executing SQLTables against large partitioned databases using Greenplum ODBC driver.

Information

 
TitleBad performance when executing SQLTables against large partitioned databases using Greenplum ODBC driver.
URL NameBad-performance-when-executing-SQLTables-against-large-partitioned-databases-using-Greenplum-ODBC-driver
Article Number000185184
EnvironmentProduct : Connect for ODBC Greenplum Wire Protocol driver
Version : All supported versions
Database : Greenplum
OS : All supported platforms
Application : All supported applications
Question/Problem Description
The SQL that gets generated by the ODBC driver when executing SQLTables or SQLColumns is not performant.
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect 41870, 42349, 44403, 44404, 44405
Enhancement Number
Cause
The generated SQL contains : AND c.relname NOT IN (select partitiontablename from pg_partitions) 
By replacing this line to : AND c.oid NOT IN ( SELECT parchildrelid FROM pg_partition_rule) 
The query will execute faster.
Resolution
Fixed in hot fix 07.16.0251.
Refer to Connect for ODBC and Connect64 hot fix download and install instructions for instructions on how to download and install the hot fix.
 
Workaround
Notes
Last Modified Date7/22/2016 1:58 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.