From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Bug #590: Migration to Postgres 7.2 impossible when capitals are used in database name |
Date: | 2002-02-15 12:06:07 |
Message-ID: | 200202151206.g1FC67b41173@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Ruud van den Brink (ruud(at)stress(dot)utwente(dot)nl) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Migration to Postgres 7.2 impossible when capitals are used in database name
Long Description
Hello,
I discovered a bug in the connect statements of postgresql 7.2. After a pg_dumpall in postgresql 7.1.3, upgrading to Postgresql 7.2 and an initdb, the following lines from the script, generated by pg_dumpall, cause a problem:
---
\connect template1 postgres
CREATE DATABASE "iBBS-oud" WITH TEMPLATE = template0 ENCODING = 'SQL_ASCII'; \connect iBBS-oud postgres
---
The database replies with:
FATAL 1: Database "ibbs-oud" does not exist in the system catalog.
The reason is, that the database is called "iBBS-oud" and not "ibbs-oud". The script contains the correct name of the database, but postgres seems to convert the capitals in "iBBS-oud" to lowercase so it becomes "ibbs-oud" internally.
It is however possible to connect to this database by means of starting psql with "psql -U postgres iBBS-oud". Connect statements in postgres itself all fail. But it's impossible to convert a set of huge databases from postgresql 7.1.3 to version 7.2
Kind regards and keep up the good work,
Ruud van den Brink.
Sample Code
No file was uploaded with this report
From | Date | Subject | |
---|---|---|---|
Next Message | Detlef Plotzky | 2002-02-15 14:07:16 | Bug with SQL-COPY in 7.2 |
Previous Message | pgsql-bugs | 2002-02-15 11:51:07 | Bug #589: JDBC KEY_SEQ in getImportedKey starts at 0 |