Message-ID: <gh-pgjdbc-pgjdbc-3505-c2651495708@github.com>
From: "cmuchinsky (@cmuchinsky)" <noreply+cmuchinsky@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 11 Feb 2025 17:11:37 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3505: Metadata queries are much slower after update to 24.7.5
In-Reply-To: <gh-pgjdbc-pgjdbc-3505@github.com>
References: <gh-pgjdbc-pgjdbc-3505@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: cmuchinsky
X-GitHub-Comment-Id: 2651495708
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3505
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3505#issuecomment-2651495708
Content-Type: text/plain; charset=utf-8

> Hey [@davecramer](https://github.com/davecramer),
> 
> I would like to double-check with you whether the below change:
> 
> if (catalog != null) {
>       sql += " AND current_database() = " + escapeQuotes(catalog);
> is a fix you guys have addressed in the latest release. I think if the answer is yes, we would need to make the appropriate change on the Liquibase side to avoid having a catalog mismatch that causes this [issue](https://github.com/liquibase/liquibase/issues/6666). Could you please let me know?
> 
> Thanks in advance, Daniel.

Is my assumption correct that the linked liquibase issue is caused by the strict equality check vs using `LIKE`? The performance is certainly worse, but the functional problem with liquibase is related to the case