Re: BUG #17111: Database created, cannot be created, but reported as inexist

From: Japin Li <japinli(at)hotmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: bernaridho(at)outlook(dot)co(dot)id, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17111: Database created, cannot be created, but reported as inexist
Date: 2021-07-17 00:11:28
Message-ID: MEYP282MB1669E99A701263EE2F65D14CB6109@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Sat, 17 Jul 2021 at 01:56, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Japin Li <japinli(at)hotmail(dot)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.
>

Thanks for your explanation.

--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2021-07-17 00:30:03 Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Previous Message Peter Geoghegan 2021-07-16 23:40:05 Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows