Re: [GENERAL] 10beta1 role
От | Adrian Klaver |
---|---|
Тема | Re: [GENERAL] 10beta1 role |
Дата | |
Msg-id | c82d1489-eeb7-0249-b682-8164f8295acd@aklaver.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] 10beta1 role (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: [GENERAL] 10beta1 role
|
Список | pgsql-general |
On 06/22/2017 01:13 PM, Jeff Janes wrote: > On Thu, Jun 22, 2017 at 12:06 PM, Ray Stell <stellr@vt.edu > <mailto:stellr@vt.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.klaver@aklaver.com
В списке pgsql-general по дате отправления: