Silly ideas, but is dropdb confusing the "postgres" user on the host and a
database named "postgres"? (does the 1st database the command was run on
still exist?) Does it do it right if the -U and -W switches are used?
Steve
On 29 June 2010 22:38, Geoffrey wrote:
> Tom Lane wrote:
>
>> Adria
Tom Lane wrote:
Adrian Klaver writes:
On Tuesday 29 June 2010 1:04:27 pm Geoffrey wrote:
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??
Adrian Klaver writes:
> On Tuesday 29 June 2010 1:04:27 pm Geoffrey wrote:
>> 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??
>
On Tuesday 29 June 2010 1:04:27 pm Geoffrey 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
> tryi
On Tue, Jun 29, 2010 at 4:04 PM, Geoffrey 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
> tryin
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??
--
Until later, Geoffrey
