Re: BUG #2333: dropdb ignores the database name argument - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #2333: dropdb ignores the database name argument
Date
Msg-id 20060319021724.GC883@surnet.cl
Whole thread Raw
In response to BUG #2333: dropdb ignores the database name argument  ("kevin barnes" <vinbarnes@gmail.com>)
List pgsql-bugs
kevin barnes wrote:

> In the 8.1 release on Unbuntu 5.10 there is an error with the dropdb command
> in /usr/bin. The error manifests itself by not respecting the DBNAME
> argument. It assumes that you want to connect to a database named 'postgres'
> and ignores whatever argument you give it. The error returned is:
>
> dropdb: database removal failed: ERROR:  database "postgres" does not exist
>
> The error is actually correct, because I do not have a database named
> postgres, but the command does not work correctly.

I think what is happening here is that dropdb is trying to connect to
the postgres database to issue the DROP DATABASE command, and fails
because it doesn't exist.  I thought it was fixed not long ago to retry
by connecting to template1 if postgres didn't exist; maybe it wasn't
really done and I'm misremembering, or maybe you're using a version
without the fix (and thus you should upgrade).

The obvious workaround is to create a database named postgres.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #2333: dropdb ignores the database name argument
Next
From: Michael Meskes
Date:
Subject: Re: BUG #2330: ECPGlib: Wrong error code in case of a duplicate key violation