Database names with spaces

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Database names with spaces
Date: 1999-10-04 14:03:34
Message-ID: Pine.LNX.4.10.9910041528220.2276-100000@peter-e.yi.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I see a todo item
* Views with spaces in view name fail when referenced

I have another one for you:
* Databases with spaces in name fail to be created and destroyed despite
responses to the contrary.

A sample session:
template1=> create database "with space";
CREATEDB
template1=> \q
$ psql -d "with space"
Connection to database 'with space' failed.
FATAL 1: InitPostgres could not validate that the database version is
compatible with this level of Postgres
even though the database system as a whole appears to be at a
compatible level.
You may need to recreate the database with SQL commands DROP
DATABASE and CREATE DATABASE.
File '/usr/local/pgsql/data/base/with space/PG_VERSION' does not
exist or no read permission.

(You can't do \c with space or \c "with space" yet. That will be (is) in
the new version.)

Further investigation shows that the directory
/usr/local/pgsql/data/base/with space is totally empty.

But:
template1=> select * from pg_database;
datname |datdba|encoding|datpath
----------+------+--------+----------
template1 | 100| 0|template1
. . .
with space| 101| 0|with space
(4 rows)

template1=> drop database "with space";
DESTROYDB

Yet, the mysterious empty directory is still there.

BUG?

--
Peter Eisentraut - peter_e(at)gmx(dot)net
http://yi.org/peter-e

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-10-04 15:11:02 Status of 'now' column defaults
Previous Message Jan Wieck 1999-10-04 11:16:01 Re: [HACKERS] NULL as an argument in plpgsql functions