From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Langlois <steve(dot)langlois(at)tavve(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Is it possible to control the location of the lock file when starting postgres? |
Date: | 2016-07-19 22:01:09 |
Message-ID: | 16354.1468965669@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Langlois <steve(dot)langlois(at)tavve(dot)com> writes:
> I ran
> + /usr/bin/initdb --pgdata=/usr/xxx/databases/pgsql/data --auth=ident
> without issue however when I try to start the database it complains about the lockfile.
> FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": Permission denied
The problem is not the lock file. The problem is that it wants to create
a socket file there. You should be able to fix this by changing the value
of unix_socket_directories.
Presumably, you are working with a distro-modified version of Postgres,
because the stock sources don't use /var/run/postgresql as a socket
directory. You will likely find that your version of libpq.so also
expects /var/run/postgresql as the socket directory, so you won't be
able to make non-TCP connections without explicitly specifying /tmp
(or wherever you choose to put the socket) as the host location.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Langlois | 2016-07-19 22:35:47 | Re: Is it possible to control the location of the lock file when starting postgres? |
Previous Message | Adrian Klaver | 2016-07-19 21:58:41 | Re: Is it possible to control the location of the lock file when starting postgres? |