pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: rdhzl (@rdhzl) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3511: Performance Regression in JDBC Driver 42.7.5 - getCrossReference
Date: Wed, 28 May 2025 19:15:30 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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.

view thread (24+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] issue #3511: Performance Regression in JDBC Driver 42.7.5 - getCrossReference
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox