Message-ID: <gh-pgjdbc-pgjdbc-3511-c2917360411@github.com>
From: "rdhzl (@rdhzl)" <noreply+rdhzl@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 28 May 2025 19:15:30 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3511: Performance Regression in JDBC Driver 42.7.5 - getCrossReference
In-Reply-To: <gh-pgjdbc-pgjdbc-3511@github.com>
References: <gh-pgjdbc-pgjdbc-3511@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: rdhzl
X-GitHub-Comment-Id: 2917360411
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-05-28T19:18:54Z
X-GitHub-Issue: 3511
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3511#issuecomment-2917360411
Content-Type: text/plain; charset=utf-8

Thanks @davecramer and @vlsi .

I've attached logs from the server. Hopefully these are helpful, but I don't typically use PG logs so if there's something that's missing let me know what I need to change in my config. 

In each file I've run our Liquibase migrations up to one of the slower changelogs and then shut down the server (it's my own local dev instance and this is the only thing running against it). I also trimmed the log files down to two liquibase changelogs: 1. a database tag statement that immediately proceeds the slow changelog, and then the actual changelog in question. It's interesting everything that gets logged between the database tag and the actual constraint rename.  

[42.7.4-postgresql-2025-05-28_144633.log](https://github.com/user-attachments/files/20493856/42.7.4-postgresql-2025-05-28_144633.log)
[42.7.5-postgresql-2025-05-28_144941.log](https://github.com/user-attachments/files/20493857/42.7.5-postgresql-2025-05-28_144941.log)
[42.7.6-postgresql-2025-05-28_145215.log](https://github.com/user-attachments/files/20493855/42.7.6-postgresql-2025-05-28_145215.log)

@vlsi I'll see what I can do about additional traces/examples.