| From: | Steve Langlois <steve(dot)langlois(at)tavve(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Is it possible to control the location of the lock file when starting postgres? |
| Date: | 2016-07-19 21:49:40 |
| Message-ID: | CY1PR0701MB19327E01ACCBA3E81484ACB287370@CY1PR0701MB1932.namprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Using Postgres 9.2 with CentOS7.
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
I know I can change permissions of /var/run of course but I want to change the location of the lock file to a directory I already have access to. So I really want to change the default location of the lock file to something other than /var/run. I've checked the options to initdb as well as looking at the various files in the data directory, pg_hba.conf, pg_ident.conf, etc.
Thank you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Langlois | 2016-07-19 21:56:48 | Re: Is it possible to control the location of the lock file when starting postgres? |
| Previous Message | Adrian Klaver | 2016-07-19 21:45:39 | Re: upsert with trigger (or rule) |