Message-ID: <gh-pgjdbc-pgjdbc-3565-c2924317535@github.com>
From: "landryb (@landryb)" <noreply+landryb@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sat, 31 May 2025 05:14:23 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3565: Use query to find the current catalog instead of relying on the database in the connection URL or connection properties as this could be different if connected through a pooler or proxy
In-Reply-To: <gh-pgjdbc-pgjdbc-3565@github.com>
References: <gh-pgjdbc-pgjdbc-3565@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: landryb
X-GitHub-Comment-Id: 2924317535
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3565
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3565#issuecomment-2924317535
Content-Type: text/plain; charset=utf-8

thanks for this PR, 42.7.6 fixes a regression that was introduced with #3390.

Using 42.7.3 against a database cnx handled by pgbouncer having a different name/alias than the real database, geotools was able to list attributes/fields in a layer/table without issues, while it started failing after an update to 42.7.5.

turning `log_statement` on, i saw that the query done had `AND current_database() = 'pgbouncer_alias'` which wasn't the real table name, thus no attributes were returned and geotools failed accessing the layer geometry.

replacing 42.7.5 jar by 42.7.6 jar, everything works as before, so thanks @davecramer !