Re: "private" installation of postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: "Joshua J(dot) Kugler" <joshua(at)eeinternet(dot)com>, pgsql-general(at)postgresql(dot)org, Scott Ribe <scott_ribe(at)killerbytes(dot)com>
Subject: Re: "private" installation of postgres
Date: 2010-09-08 01:09:12
Message-ID: 16536.1283908152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

John R Pierce <pierce(at)hogranch(dot)com> writes:
> On 09/07/10 5:24 PM, Joshua J. Kugler wrote:
>>> I'm pretty sure the socket directory is hard coded in the source, I
>>> don't think you can override it even with ./configure

>> postgresql.conf:
>> unix_socket_directory = '/var/run/postgresql'

> for some reason, I'm remembering that last time I looked, there were
> places where this value wasn't being used.

The client side is obviously not going to know what is in the server's
config file, so you're going to have to specify that path every time you
connect. Depending on what you are doing, you might want to build a
version of libpq that defaults to assuming the nondefault socket
location rather than /tmp. If so, edit DEFAULT_PGSOCKET_DIR in
src/include/pg_config_manual.h.

Personally, though, I think it's easier to change the default port
number and not worry about sharing /tmp. Changing the port is a good
idea anyway to avoid any possible conflicts on shared memory IDs.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Ribe 2010-09-08 01:19:38 Re: "private" installation of postgres
Previous Message Scott Ribe 2010-09-08 00:53:15 Re: "private" installation of postgres