From: Tom Lane <tgl@sss.pgh.pa.us>
To: m.kristo@rewe-group.at
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19043: jdbc connection url is not case insensitive
In-reply-to: <19043-e6955a06c7befbf7@postgresql.org>
References: <19043-e6955a06c7befbf7@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 05 Sep 2025 06:28:15 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1529703.1757107206.1@sss.pgh.pa.us>
Date: Fri, 05 Sep 2025 17:20:06 -0400
Message-ID: <1529704.1757107206@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1529704.1757107206%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> when creating a database in Postgres with the name e.g. "testDB", postgres
> creates a database in lowercase testdb.
> So far so good, but when trying to connect via psql and passing as database
> name "testDB" the connection fails, because it says the database does not
> exists.
> In my opinion, the libq library should also be case insensitive and
> automatically convert this to a lowercase "testdb" and not return an error.

Then it would become impossible to connect to databases that have
upper-case or mixed-case names.

Our general position on such matters is that automatic downcasing
happens in SQL commands, but not in any other context (such as
command-line arguments or connection strings).

			regards, tom lane