Re: 10beta1 role

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Ray Stell <stellr(at)vt(dot)edu>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: 10beta1 role
Date: 2017-06-22 20:22:08
Message-ID: c82d1489-eeb7-0249-b682-8164f8295acd@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/22/2017 01:13 PM, Jeff Janes wrote:
> On Thu, Jun 22, 2017 at 12:06 PM, Ray Stell <stellr(at)vt(dot)edu
> <mailto:stellr(at)vt(dot)edu>> wrote:
>
> I used "initdb -U" to specify an alternate superuser. On startup it
> throws these msgs:
>
> 2017-06-22 14:36:34 EDT,0,startup FATAL: 28000: role "postgresql"
> does not exist
>
> 2017-06-22 14:36:34 EDT,0,startup LOCATION: InitializeSessionUserId,
> miscinit.c:503
>
>
> Earlier versions do the same thing if you start them with the wait
> option (-w).
>
> The difference is that wait is now the default, and you use -W to turn
> it off.

The would seem to work for the pg_ctl init[db] mode, however the OP is
using the plain initdb where -W is:

-W
--pwprompt

Makes initdb prompt for a password to give the database superuser.
If you don't plan on using password authentication, this is not
important. Otherwise you won't be able to use password authentication
until you have a password set up.

Would that still work?

>
> With the wait option in use, when starting up the server pg_ctl keeps
> trying to connect to the server so once it is running, it can report
> success. But it doesn't know who to connect as, so it just uses the default.
>
> Cheers,
>
> Jeff

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2017-06-22 20:29:03 Re: 10beta1 role
Previous Message Ray Stell 2017-06-22 20:18:34 Re: 10beta1 role