| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | krishmba06(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16416: unable to start the server with pg_CTL |
| Date: | 2020-05-05 08:37:50 |
| Message-ID: | 233F6064-C54A-497C-8419-BA4EDE8A406F@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 5 May 2020, at 08:28, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> Any suggestions here will be really helpful- thanks.
The error is quite likely to be the one pg_ctl tells you:
> pg_ctl start -D /Library/PostgreSQL/12/data waiting for server to
> start....2020-05-05 11:40:04.838 IST [1216] FATAL: data directory
> "/Library/PostgreSQL/12/data" has wrong ownership 2020-05-05 11:40:04.838
> IST [1216] HINT: The server must be started by the user that owns the data
> directory. stopped waiting pg_ctl: could not start server Examine the log
> output.
The permissions are probably still not quite right for the user with which you
are trying to start the server.
If you initdb a fresh database you can inspect the permissions being set there
as a point of reference.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-05 18:59:17 | Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering |
| Previous Message | PG Bug reporting form | 2020-05-05 07:25:33 | BUG #16417: Unable to connect to server |