Re: BUG #3711: dropdb and creatdb with pgpass.conf file - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #3711: dropdb and creatdb with pgpass.conf file
Date
Msg-id 4728F5E2.6090800@enterprisedb.com
Whole thread Raw
In response to BUG #3711: dropdb and creatdb with pgpass.conf file  ("gregory vallet" <gvallet@fr.abx.fr>)
List pgsql-bugs
gregory vallet wrote:
> In order to automatized the password on commands like pg_dump, dropdb and
> creatdb, I created a pgpass.conf file with
> "localhost:5432:02HH65:superuser:xxxxxxx"
>
> With the pg_dump command, it's OK
> with dropdb and creatdb, system asks me for the password.
>
> If I replace "02HH65" with "*" like "localhost:5432:*:superuser:xxxxxxx",
> it's OK for dropdb and creatdb.
>
> Why do dropdb and creatdb can't recognize my database name?

createdb and dropdb are different from pg_dump and other commands in
that it always connects to the "postgres" database (or "template1", if
you're deleting or creating the postgres database), not your application
database, to execute the "CREATE DATABASE" or "DROP DATABASE" command.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "gregory vallet"
Date:
Subject: BUG #3711: dropdb and creatdb with pgpass.conf file
Next
From: Tom Lane
Date:
Subject: Re: BUG #3711: dropdb and creatdb with pgpass.conf file