Message-ID: <gh-pgjdbc-pgjdbc-3390-c2531879821@github.com>
From: "SophiahHo (@SophiahHo)" <noreply+SophiahHo@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 10 Dec 2024 14:56:34 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
In-Reply-To: <gh-pgjdbc-pgjdbc-3390@github.com>
References: <gh-pgjdbc-pgjdbc-3390@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: SophiahHo
X-GitHub-Comment-Id: 2531879821
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3390
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3390#issuecomment-2531879821
Content-Type: text/plain; charset=utf-8

@davecramer When our enterprise customers upgraded their pgjdbc driver from a version older than 42.7.0 to a version between 42.7.0 and 42.7.4, they are getting [duplicated database objects for metadata queries.](https://github.com/pgjdbc/pgjdbc/issues/3389#issuecomment-2414487622) As a workaround, we asked our enterprise customers to downgrade their pgjdbc driver to a version before 42.7.0. This MR fixes this bug so that our enterprise users would be able to use the latest pgjdbc driver with security updates.