Re: How should the first step of PostgreSQL implementation should be? (revised) - Mailing list pgsql-general

From Alban Hertroys
Subject Re: How should the first step of PostgreSQL implementation should be? (revised)
Date
Msg-id 9E9047F1-2B1A-4A9C-9308-69980D259A1F@solfertje.student.utwente.nl
Whole thread Raw
In response to Re: How should the first step of PostgreSQL implementation should be? (revised)  (Ricky Tompu Breaky <ricky.breaky@uni.de>)
Responses Re: How should the first step of PostgreSQL implementation should be? (revised)
List pgsql-general
On 27 Sep 2009, at 10:44, Ricky Tompu Breaky wrote:

> RB>I forgot to show you that I've done these steps too:
> postgres=# ALTER ROLE ivia WITH LOGIN;
> ALTER ROLE
> postgres=# alter user ivia with password '<<my password>>';
> ALTER ROLE
> postgres=# alter user ivia with login;
> ALTER ROLE
> postgres=# commit;
> WARNUNG:  keine Transaktion offen
> COMMIT
> postgres=# \q
> sussy:~ # psql -h 127.0.0.1 -U ivia -W
> Password for user ivia:
> psql: FATAL:  Datenbank »ivia« existiert nicht
> sussy:~ #


You didn't specify a database to connect to. By default psql tries to
connect to a database named after the login user, in this case "ivia".
You probably want to connect to the database named "postgres" that's
created by default (at the initdb step).

Alban Hertroys

--
Screwing up is the best way to attach something to the ceiling.


!DSPAM:737,4abf320b11688043321471!



pgsql-general by date:

Previous
From: Ricky Tompu Breaky
Date:
Subject: Re: How should the first step of PostgreSQL implementation should be? (revised)
Next
From: Scott Marlowe
Date:
Subject: Re: How should the first step of PostgreSQL implementation should be?