| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Geoffrey <lists(at)serioustechnology(dot)com> |
| Cc: | PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: dropdb weirdness |
| Date: | 2010-06-29 20:20:26 |
| Message-ID: | AANLkTikOXr9q5lkU4azn54gaD4J2lbstLctzdQGkehQO@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 29, 2010 at 4:04 PM, Geoffrey <lists(at)serioustechnology(dot)com> wrote:
> So running the following command:
>
> dropdb -p 5443 swr
>
> I get:
>
> dropdb: could not connect to database postgres: FATAL: database "postgres"
> does not exist
>
> Why is it not 'seeing' the database name I'm passing to it? Why is it
> trying to drop a database named postgres??
It's not. It's trying to log into the postgres database to execute the
command. Try logging into the database via psql you want to issue
the 'drop database' sql FROM (usually template1 / postgres) and do the
drop database yourself. You can't drop the database you are logged in
to.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2010-06-29 20:22:47 | Re: dropdb weirdness |
| Previous Message | Geoffrey | 2010-06-29 20:04:27 | dropdb weirdness |