Message-ID: <gh-pgjdbc-pgjdbc-3568-c2772418913@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 02 Apr 2025 12:33:05 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3568: use pgType instead of internal name to preserve the schema
In-Reply-To: <gh-pgjdbc-pgjdbc-3568@github.com>
References: <gh-pgjdbc-pgjdbc-3568@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2772418913
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-04-02T12:59:10Z
X-GitHub-Issue: 3568
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3568#issuecomment-2772418913
Content-Type: text/plain; charset=utf-8

```
select 'public'= any(current_schemas(false));
 ?column?
----------
 t
```
can tell us if public is on the search path, but I'm loathe to query the database every time
We could update it in setSchema which would catch quite a few cases, but not all. Users are still free to execute `set search_path` on their own