Re: initdb using option "username" startup log - Mailing list pgsql-bugs

From Tom Lane
Subject Re: initdb using option "username" startup log
Date
Msg-id 28870.1351655910@sss.pgh.pa.us
Whole thread Raw
In response to initdb using option "username" startup log  (Dae-man Yang <yangsclub@gmail.com>)
Responses Re: initdb using option "username" startup log  (Dae-man Yang <yangsclub@gmail.com>)
List pgsql-bugs
Dae-man Yang <yangsclub@gmail.com> writes:
> I initdb like below
> "initdb --pgdata=/pg_data --encoding='utf8' --locale='C' --lc-collate='C'
> --lc-ctype='C' --username=sys --pwprompt"

OK.  The --username switch specifies the name of the initial database
superuser.  Instead of "postgres", it's going to be "sys".

> When startup database server.
> Server wirte log like this
> -----------------------------
> LOG:  database system was shut down at 2012-10-31 12:00:14 KST
> LOG:  database system is ready to accept connections
> LOG:  autovacuum launcher started
> FATAL:  role "postgres" does not exist
> -----------------------------

> *What is it ? : FATAL:  role "postgres" does not exist*

That would be the trace of something trying to connect as user
"postgres", which doesn't exist because you told initdb to create "sys"
instead.  The database is up and running, but you'll only be able to
connect to it by specifying the username "sys" (at least until you make
some more database roles).

            regards, tom lane

pgsql-bugs by date:

Previous
From: Dae-man Yang
Date:
Subject: initdb using option "username" startup log
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations