From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | bernaridho(at)outlook(dot)co(dot)id |
Subject: | BUG #17111: Database created, cannot be created, but reported as inexist |
Date: | 2021-07-15 22:04:41 |
Message-ID: | 17111-c66d4212978a0260@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17111
Logged by: Bernaridho Hutabarat
Email address: bernaridho(at)outlook(dot)co(dot)id
PostgreSQL version: 12.7
Operating system: CentOS
Description:
postgres=# \c Database
FATAL: database "Database" does not exist
Previous connection kept
postgres=# CREATE DATABASE Database;
ERROR: database "database" already exists
postgres=# DROP DATABASE Database;
DROP DATABASE
postgres=# CREATE DATABASE Database OWNER ServiceUser1;
CREATE DATABASE
postgres=# \c Database;
FATAL: database "Database" does not exist
Previous connection kept
postgres=# DROP DATABASE Database;
DROP DATABASE
postgres=# CREATE DATABASE Database OWNER postgres;
CREATE DATABASE
postgres=# \c Database;
FATAL: database "Database" does not exist
Previous connection kept
postgres=# DROP DATABASE Database;
DROP DATABASE
postgres=# \q
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2021-07-15 22:59:45 | Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange |
Previous Message | Alvaro Herrera | 2021-07-15 21:33:20 | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |