Re: BUG #17111: Database created, cannot be created, but reported as inexist - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17111: Database created, cannot be created, but reported as inexist
Date
Msg-id 3745704.1626458183@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17111: Database created, cannot be created, but reported as inexist  (Japin Li <japinli@hotmail.com>)
Responses Re: BUG #17111: Database created, cannot be created, but reported as inexist  (Japin Li <japinli@hotmail.com>)
List pgsql-bugs
Japin Li <japinli@hotmail.com> writes:
> Can we remove the code for compatibility with 7.2 or older?

I'm kind of inclined not to, because most other ways that you can
specify a database name for a connection also don't downcase.

$ psql Postgres
psql: error: connection to server on socket "/tmp/.s.PGSQL.5440" failed: FATAL:  database "Postgres" does not exist

$ psql postgres
...
postgres=# \c "dbname=Postgres"
connection to server on socket "/tmp/.s.PGSQL.5440" failed: FATAL:  database "Postgres" does not exist
Previous connection kept

This largely stems from an ancient decision that we shouldn't
auto-downcase names coming from a program's command line.
The interaction of SQL and shell quoting conventions is messy
enough that specifying a non-lower-case database, user, etc name
would be pretty annoying if we did do that.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size