pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
Date: Wed, 19 Feb 2025 12:46:29 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

> > , or whatever is returned in the startup parameters
> 
> It looks like the startup parameters do not return the database name.

Interesting, somehow I though it was.
> 
> At the same time, there's `current_catalog` function and `information_schema.information_schema_catalog_name` table returning `catalog_name` which is **different** from `current_database`.
> 
> So it looks like we should use those functions rather than `current_database()` if we want to treat catalogs somehow. Is there a reason to ignore `current_catalog` PostgreSQL function?

Only if it creates a performance regression.

view thread (31+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox