From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Murray Cumming <murrayc(at)murrayc(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Disable unix-domain sockets? |
Date: | 2012-10-25 13:40:04 |
Message-ID: | 26319.1351172404@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Murray Cumming <murrayc(at)murrayc(dot)com> writes:
> I hoped that if I didn't use "local" in my pg_hba.conf file, instead
> using just "host", then postgresql might not allow unix socket
> connections at all, so it wouldn't need to create that .lock file.
> http://www.postgresql.org/docs/9.2/static/auth-pg-hba-conf.html
> But postgres still tries to create the .lock file, failing here on
> Fedora because it defaults not to /tmp but to /var/run/postgresql, which
> the local user can't write to.
If you are using a version that defaults to /var/run/postgresql, then
it is new enough to have the unix_socket_directories parameter. Setting
that to empty should do the trick. pg_hba.conf is not the place to
configure which ports/sockets PG listens on.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | jo | 2012-10-25 13:50:08 | migrate from PostgreSQL to Oracle |
Previous Message | Heiko Wundram | 2012-10-25 11:52:09 | Re: Somewhat automated method of cleaning table of corrupt records for pg_dump |