Re: BUG #15108: Initialization problem postgresql-10-setup initdb - Mailing list pgsql-bugs

From alertas
Subject Re: BUG #15108: Initialization problem postgresql-10-setup initdb
Date
Msg-id b1af0497-7164-0c35-c839-041840836640@click-it.es
Whole thread Raw
In response to BUG #15108: Initialization problem postgresql-10-setup initdb  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15108: Initialization problem postgresql-10-setup initdb  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-bugs
Hi,

I don't understand, in the official documentation appear "initdb must be run as the user that will own the server process, because the server needs to have access to the files and directories that initdb creates. Since the server cannot be run as root, you must not run initdb as root either. (It will in fact refuse to do so.)"

Regards,

El 14/03/18 a las 16:59, Devrim Gündüz escribió:
Hi,

On Tue, 2018-03-13 at 12:12 +0000, PG Bug reporting form wrote:
The problem is reported when executing database initialization command,
postgresql-10-setup initdb.
In the official documentation
(https://www.postgresql.org/docs/10/static/app-initdb.html) indicates that
it must be executed with the user postgres, but the command only works if I
execute it as root.

This command does not
postgresql-10-setup is a wrapper around initdb (which solves many problems), 
*not* the initdb binary, and needs to be run as root. You can always run initdb
directly with:

/usr/pgsql-10/bin/initdb

Regards,


pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: Postgres 10.3 delete on partition table cannot execute, out ofmemory.
Next
From: Yavuz TANRIVERDİ
Date:
Subject: Re: contrib/start-scripts/freebsd script fails with Ambiguous output redirect.