Message-ID: From: "desruisseaux (@desruisseaux)" To: "pgjdbc/pgjdbc" Date: Wed, 25 Jun 2025 11:34:43 +0000 Subject: Re: [pgjdbc/pgjdbc] issue #3685: Regression: a query does not work anymore on connection created by `PGSimpleDataSource` but still work with `DriverManager` In-Reply-To: References: List-Id: X-GitHub-Author-Login: desruisseaux X-GitHub-Comment-Id: 3004445747 X-GitHub-Comment-Type: issue_comment X-GitHub-Issue: 3685 X-GitHub-Repo: pgjdbc/pgjdbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3685#issuecomment-3004445747 Content-Type: text/plain; charset=utf-8 > You are conflating psql and pgjdbc. They are not the same I know that they are not the same. My argument is that: 1. The addition of a `?currentSchema=features` option in the URL is the only significant difference I could see in the comparison of the `pgjdbc` logs of the two tests posted in [above comment](https://github.com/pgjdbc/pgjdbc/issues/3685#issuecomment-3000511929). 2. That `?currentSchema=features` option is not accepted by `psql`. Error message is: _psql: erreur : paramètre de la requête URI invalide : « currentSchema »_. 3. I did not found `currentSchema` in the list of parameters accepted in the `?foo=bar` part of an URI according [PostgreSQL documentation](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS), contrarily to other parameters such as `?user` and `connect_timeout`. 4. We do observe that when the `?currentSchema` parameter is specified, PostgreSQL 16 or PostGIS do not behave correctly. 5. Therefore, I suspect that `?currentSchema` is not officially supported. Maybe it is a deprecated parameter. Unless one of the above points is wrong, I thing that `PGSimpleDataSource.setCurrentSchema` should be deprecated.