Message-ID: <gh-pgjdbc-pgjdbc-3565-c2772628381@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 02 Apr 2025 13:49: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: davecramer
X-GitHub-Comment-Id: 2772628381
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-2772628381
Content-Type: text/plain; charset=utf-8

> It would be great if `catalog_name` was `GUC_REPORT`. The bouncer could emit notifications if the `catalog_name` ever changed.

That is really a pg_bouncer problem. In reality the server will never change the catalog once the connection is established. I think we could get pg_bouncer to emit `database` however.