Message-ID: <gh-pgjdbc-pgjdbc-3511@github.com>
From: "danielhasan (@danielhasan)" <noreply+danielhasan@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 05 Feb 2025 14:14:13 +0000
Subject: [pgjdbc/pgjdbc] issue #3511: Performance Regression in JDBC Driver 42.7.5 - getCrossReference
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Id: 15160101
X-GitHub-Author-Login: danielhasan
X-GitHub-Issue: 3511
X-GitHub-Milestone: 42.7.8
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-State: closed
X-GitHub-Type: issue
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3511
Content-Type: text/plain; charset=utf-8

I am reporting a performance issue encountered with the JDBC driver version 42.7.5 when using the getCrossReference method from the DatabaseMetaData interface. 

Issue:
In version 42.7.5, the execution time for getCrossReference has significantly increased. Specifically, the recovery time has gone from approximately 1 second in version 42.7.4 to 15 seconds when querying against a database with 450 tables.

Steps to Reproduce:

Use JDBC driver version 42.7.5.
Call the getCrossReference method on the DatabaseMetaData instance for a schema containing 450 tables.
Observe the time taken for the operation.
Expected Behavior:
The expected response time for the getCrossReference call using version 42.7.4 is approximately 1 second.

Actual Behavior:
The actual response time in version 42.7.5 has increased to approximately 15 seconds.

Environment:

JDBC Driver Version: 42.7.5
Previous Version (for Comparison): 42.7.4
Database Size: 450 tables
Recommendation:
Please investigate the performance degradation introduced in version 42.7.5 and consider reverting any changes that may have impacted the efficiency of the getCrossReference method.

Thank you for looking into this matter.